Team
A small studio with named roles, and senior advisors who challenge what we are doing. No account managers, no bench, nobody you will never meet.
Structure
Four to six technical co-founders is a specific failure pattern: everybody wants to build, nobody owns selling, and revenue never arrives. So each role has a person against it.
The final call when the team deadlocks. The numbers, the bank account, the monthly review.
Enquiries, proposals, follow-ups. Bills less as a result — that is the job, not a shortfall.
Scope, estimates, schedules, the weekly client demo. Says no to scope creep so engineers do not have to.
Architecture, code review, the standard stack. Guards quality when deadlines press.
Invoicing, contracts, compliance, tools. Four hours a week, and painful when it is nobody's job.
Leadership
Five roles, assigned by name. One person may hold two; no role is held by nobody — which is the failure pattern for a team of technical co-founders.
Co-founder · Engineering
Full-stack and mobile engineer. Built the learning platform this studio is known for — web and mobile on a single API, traced to a formal specification and shipped with four role-based manuals.
OwnsArchitecture, code review, the standard stack, engineering practice
Profiles appear here once the person has confirmed in writing. That matters most for advisors: listing an academic title and institution implies an endorsement the institution has not given, so we ask first.
Edit src/content/team.ts and set cleared: true.
We are a small team and we hire slowly. If you build the way we do, say hello.