Solo Senior Dev vs. Agency: A Founder's Choice
Should you hire one senior engineer or an agency? I've seen both paths. Here's a look at the real trade-offs.
I'm Maria Tomeian, a senior full-stack engineer, fourteen years. No sales layer, no project telephone. You brief me, I build it, and the person you talk to on day one is the person who ships on day ninety.
Tomeian is my surname. Read in Japanese, it becomes tōmei-an, 透明庵: “the transparent hermitage.” 透明 is transparency. 庵 is the small studio of a master: the suffix poets and tea masters gave the huts where they worked alone.
A name I was born with that describes the studio I built: nothing hidden. No layers between you and the work, no markup on invisible people, no translation loss.
In old Japan, a samurai without a lord was called rōnin. This studio answers to no agency, only to the work.
Your brief passes through a salesperson, an account manager and a project owner before it reaches whoever writes the code. Every handoff costs a week and half the meaning.
I do. Fourteen years of shipping, with AI doing the grunt work under my supervision. The Japanese call it shokunin: the craftsman who masters the tools, not the other way around.
Rebuilt the content system behind one of the UK's most-visited slots review sites. Millions of monthly visitors on my code.
AI booking and WhatsApp platform for independent rental operators. In build, first market: Italy. Every pixel mine.
Outreach and pipeline automation for an Italian growth agency. Cold-to-warm handled by machines, closing left to humans.
MOST WORK IS CLIENT-OWNED OR UNDER NDA. ASK FOR A WALKTHROUGH ON A CALL →
THE AGENTS MULTIPLY THE OUTPUT. THE HUMAN OWNS THE RESULT.
Fixed scope or monthly. You see the number before the work starts, not after.
A few clients at a time. Real attention and honest timelines, not a bench.
The person on the first call is the person who ships. That is the whole business model.

Should you hire one senior engineer or an agency? I've seen both paths. Here's a look at the real trade-offs.

A quick feasibility call can prevent costly mistakes in software development. Understand true project scope and avoid dead ends before you invest heavily.

I often build client websites and their content management systems as separate applications. But a single Next.js app running Payload CMS can simplify that.
A 30-minute call. You describe what you're building; you leave with an honest read and a rough estimate. If I'm not the right person for it, I'll tell you on the call, not after three meetings.