// why · why this exists
Most ideas never see the light of day. Talk, talk, talk.
Ten years on the client side of software projects — strategy decks, vendor reviews, steering committees. Now I build them too. Same chair from brief to production.
For ten years I sat in software projects from the client side. Strategy decks, vendor reviews, RFPs, steering committees. Watching great ideas die in the gap between the people who needed them and the people who built them.
The translation never worked. Business asked for outcomes; engineering heard requirements. Engineering shipped requirements; business got something that technically met the spec and missed the point. Six months later, a retrospective, a "lessons learned," and a new vendor. Repeat.
Let's change the loop. Talk once. Build for a couple of hours. Talk again. Iterate.
That's what this is named after — and what it's for.
// what I'm frustrated by
Specifically.
Agencies that ship Jira tickets instead of working software. Velocity dashboards aren't a deliverable.
Consultancies that recommend but won't build. A 200-page deck is not the same as a thing that runs in production.
Vibe-coded MVPs with no architecture underneath. They demo well on a Tuesday and fall over on a Thursday.
Lovable prototypes treated like production systems. Lovable is fast; the backend, auth, MCP layer, SEO, and handoff discipline still need a senior owner.
AI demos that never ship. Looks great on LinkedIn, never makes it to a customer.
Juniors-plus-AI as a delivery model. AI is fastest in the hands of seniors who can tell when it's wrong. Without that, it's a defect factory with autocomplete.
Six-month timelines for things that should ship in weeks. The estimate isn't the work — it's the ceremony around the work.
If any of that sounds familiar, you already know why I started this.
// the wedge
Both sides of the table, one person, no translation loss.
Ten years inside enterprise software projects. Not building — running them, advising on them, sitting in the rooms where they get scoped, killed, or revived. I know what business stakeholders actually want, how they decide, and where the translation breaks.
Now I build them too. Top 0.5% AI-accelerated and Lovable developer. 50+ AI applications shipped. The studio brings in specialists when a project genuinely needs them — design depth, infra, specialist domains — but the same chair owns the line from "what should we build" to "what's running in production."
There is no handoff between the consultant and the developer because they're the same person.
// what I believe
What I believe.
- 01
Builders beat advisors.
A recommendation you haven't shipped is a hypothesis. I'd rather hand you a working version of the answer than a deck about it.
- 02
AI accelerates the bulk, judgment guards the edges.
AI does the implementation lift. Architecture, security, what-not-to-build, and how Lovable connects to real systems through MCP — that stays human, and it stays senior.
- 03
Speed and quality stop being a tradeoff
when the team is small and the loop is short. The tradeoff is a project-management artifact, not a law of physics.
- 04
Production is the only proof.
Demos, prototypes, decks, and stand-ups are scaffolding. If it isn't running where customers can hit it, it doesn't count.
- 05
Frustration is a roadmap.
Every "that's just how it works" is a place where someone gave up. Those are the highest-leverage spots to build something better.
// how I work
How I work.
Days to a working prototype. Weeks to something in production. Not quarters.
One person owns the arc. Strategy, scoping, design decisions, and code come from the same chair. The studio adds people when scope demands it — not by default.
AI tooling on the inside, senior judgment on the outside. I ship what AI generates; I don't merge what AI guesses.
You can call the person who wrote the code. That's me. Always.
// who this is for
- Founders who need to ship now and don't have time for a six-week kickoff.
- Exec teams stuck mid-translation, where the engineering org and the business org keep talking past each other.
- Companies adopting AI tooling — Lovable, Cursor, Claude, MCP — that want the speed without the quality cliff.
- Lovable teams that need a top-ranked developer to connect generated frontends to production backends, APIs, and MCP workflows.
// who this isn't for
- Buyers who need a 200-page deck before any code exists.
- Engagements measured in headcount rather than outcomes.
- Projects that require a twelve-person ceremony before a button gets clicked.
If you're either of those, no offence — I'm just not the right shape.
// a small note on the name
The mark is a tulip with an Fgrown into the stem. There's a personal anchor in there I won't unpack on a marketing page.
What's worth saying: it's why "frustration" isn't a marketing word for me. It's the thing that turned watching projects fail into building them differently. The mark is dignified on purpose. So is this.
Bring me your frustration.
Tell me what isn't shipping, what's stuck, or what you keep getting estimates for that never come back smaller. I'll tell you on the call whether I'm the right person — and if I'm not, I usually know who is.
I reply within a day — faster if you're on fire.