FAQ · honest answers

Questions, answered straight.

The things businesses ask before working with me — what I build, what it costs, what happens to your data, and whether you're locked in. No spin. If the answer is "it's not a fit," that's in here too.

What does saulera actually do?

I build AI systems that do the repetitive work your team keeps doing by hand — the re-keyed spreadsheet, the inbox that runs your day, the report that eats a morning. I scope one job, build a system that does it, document it, and hand it over. You keep the result.

Is this for a business my size?

Yes — small and medium businesses are who I build for. Owner-run operations running on spreadsheets, Gmail and patience, where the same job gets done by hand every week. If there's something you'd love to stop doing manually, it's probably a fit. If it isn't, I'll tell you.

What's "first build, no fee" — what's the catch?

No catch. I open by building one real fix, at no cost, instead of pitching it. The fix is yours either way. If it earns your trust, we talk about what's next. If it doesn't, the build is still yours — no obligation, no follow-up funnel. I'd rather show you than tell you.

How much does it cost, and how long does it take?

Every build is scoped to the job, so I price it once I've seen the work — not from a menu. You get a fixed price and a fixed timeline before anything starts. Most engagements run two to sixteen weeks depending on scope, shipped in stages, not open-ended. And the first build carries no fee.

What happens after you build it — am I locked in?

No retainer trap. Every build ships with a runbook and a clean exit — your team runs it after I leave. You get thirty days of support to settle it in, and optional help later only if you want it. I document so you don't depend on me. That's the point.

Is my data safe?

Yes — it's the first thing I design for. I work inside your own tools and accounts, I don't move data where it doesn't belong, and I build to UK and EU data rules (GDPR). Before anything starts, I walk you through exactly what touches what.

Which AI model do you build on — am I tied to one vendor?

None in particular, and no. Every system I build is LLM-agnostic — it can run on OpenAI, Anthropic or a locally hosted model, and it's designed so the model underneath can be swapped without rebuilding the system. If your data policy needs a specific vendor, a UK or EU region, or a model that never leaves your own infrastructure, the build follows your rules. You're never tied to one AI company's pricing or terms.

Will this replace my staff?

No. It does the repetitive work — the re-keying, the chasing, the copy-paste — so your people spend their time on the work that actually needs them. It gives your team hours back, not a smaller team.

Isn't AI just hype — how is this different?

Fair question. I don't pitch agentic systems — I run my own studio on one, every day. I build the thing, show it working, and hand it over. If AI won't actually help your job, I'll say so. Evidence first, honest answer either way.

Why you, and not a bigger agency?

saulera is me. The person who takes your brief is the person who builds it and hands it over — no account manager, no junior doing the real work, no consultancy bloat. Ten years building martech for global brands, now building for businesses your size.

How do we start?

A thirty-minute call. You tell me one job you'd love to stop doing, I ask three questions, and I tell you what shipping it would take — or that it isn't a fit. No funnel, no pressure.

What kinds of jobs do you automate?

The common ones: a customer-response agent that drafts replies to enquiries; the recurring report or spreadsheet, automated; a lead-response system so no enquiry goes cold; a content engine that turns one idea into a week of scheduled posts. But I start from your job, not a template — tell me what eats your week and I'll tell you if I can take it off your plate.

Do I need a tech team, or to be technical myself?

No. I build for handover — plain runbook, your existing tools, your team. If you can use email and a spreadsheet, you can run what I build.

What if it breaks, or I need changes later?

Every build ships documented, so your team can handle small things themselves. Thirty days of support is included to catch anything early. After that, you can call me back for changes when you want them — by choice, not on a contract that never ends.

Do you have client case studies?

Honestly, I'm early — and I say so. The systems on my site are built and running, not paid client engagements, and every one is open to a walkthrough. That's exactly why I open with a free build: proof you can watch work, before you pay.

Where are you based, and which languages do you work in?

East Grinstead, West Sussex — and Latvia. Working with businesses in both, and remotely where it suits. In English and Latvian.

Still wondering if your job is a fit?

Book a 30-minute review