saulera is an ai-agentic build studio for small and medium businesses.
founded in 2026 by linards bērziņš. dual-based in east grinstead, uk and riga, latvia. small by choice — one operator who ships.
founded2026
basedeast grinstead · riga
teamsolo studio
working languageenglish · latvian · spanish
i — depth
twelve years of martech depth.
senior email developer at merkle / dentsu — the engineering work behind email and data programmes for global brands. the systems that move money, not the slide decks that promise to. it taught one durable lesson: the work that compounds is the work that ships. the rest is theatre.
ii — the agentic shift
the agentic shift.
as large language models matured into agentic systems, two things became obvious. most ai consulting wouldn't ship anything real. and most enterprise ai tooling would never reach the businesses that needed it most — the small and medium operators running on spreadsheets, gmail, and patience. saulera is the bridge: agentic engineering applied to small-and-medium operations. five real systems already shipped or shipping — see the results page for the full inventory.
iii — dual-based
dual-based by design.
working from east grinstead, uk and riga, latvia. comfortable with cross-border engagements (uk ↔ baltic ↔ eu), with project access into argentina via family network for clients with south american touchpoints. the timezone overlap, language coverage, and operational rigour are deliberate — not accidental.
working principles
discipline holding the optimism. four rules we don't break.
we ship working software.
not slide decks, not strategy memos, not roadmaps with question marks at the end. you hire a build studio because something needs to exist by friday. that's the deal we keep.
we say no to engagements that won't ship.
if the scope is wrong, the budget too thin, or the org not ready — we say so in the build review. a clean no preserves trust longer than a polite yes.
british english, local pricing.
"colour", "optimise", "realised". gbp, eur, ars as the engagement requires. small details, but they signal who we work with — and who we don't.
we document so you don't depend on us.
every workflow ships with a runbook. every app ships with handover docs. the goal is a system your team can run after we leave — not a retainer trap.
think we're the right shape for what you need built?
30 minutes. one workflow. honest answer either way.