Start with a clear picture. Then build.
Every engagement starts with a one-week Technical Assessment. From there, I build new products, own the engineering on live ones, or fix what needs fixing.
Technical Assessment
1 WEEKOne week. A clear picture of what your product has, what it needs, and what that takes. The plan is yours to keep.
Every engagement with me starts here. Before you build the next big feature, hire engineers, commission a rewrite, or close a technical acquisition, you need a clear, honest picture of the codebase. In one week I read every file, map the architecture, run a security pass, audit the dependencies, and deliver a written risk register with plain-English findings and realistic effort estimates. You get a prioritised plan and a 30-minute recorded walkthrough for you and your team. The plan is yours to keep whether we work together afterwards or not, and the fee is credited in full toward any follow-on engagement.
SaaS Engineering Partnership
MONTHLYI own the technical side of your SaaS, month by month.
Once a product has paying customers, someone has to keep building it. The SaaS Engineering Partnership gives you 40 hours of dedicated engineering per month: feature sprints, performance improvements, third-party integrations, scaling work, and async support. No hiring overhead, no equity, no six-month notice period. You get a senior engineer who already knows your codebase, owns the technical side, and stays with it when a sprint gets hard.
SaaS Product Build
6-8 WEEKSA new SaaS product, built to production standards from day one. Fixed scope, weekly demos, and I stay responsible for it.
Most new products do not fail on bad code. They fail on a scope that shifts every week until month four delivers a prototype instead of a product. This engagement is the opposite: a signed scope of work before any code exists, a phased plan with a concrete deliverable every Friday, and a production-grade stack from day one: real authentication, real billing, real observability. It is built the same way I built my own B2B SaaS, Carrier Intelligence: millions of records, sub-second search, and Stripe billing, solo from zero to production. Whether 6 to 8 weeks is realistic for your product is something I will tell you on the first call, not in week six.
AI Prototype Rescue
Take an AI-built prototype to a product real customers can rely on.
Lovable, Cursor, v0, and Bolt can produce a convincing prototype in an afternoon. What they cannot produce is a system that handles 50 concurrent users, processes real Stripe webhooks without data loss, or stores customer information without exposing it. If you have an AI-generated codebase that works in your screen recording but not yet for real users, this is where the engagement starts. Week one is a written technical assessment you receive before we scope the rest. You decide what to keep, what to replace, and what the budget looks like. I refactor only what will cause a real production failure. No rewrites for vanity.
AI Development
RAG pipelines, LLM features, and AI agents built with real evals, not vibes.
The gap between an AI demo that impresses investors and an AI feature that works reliably for real users is an evaluation framework. Without evals, you are guessing whether retrieval is returning useful chunks, whether your prompts degrade when the model updates, and whether your agent actually completed the task or just said it did. I build AI features with measurement from day one: retrieval evals before any prompt engineering, distributed traces on every agent run, cost ceilings per execution, and a regression suite that catches model regressions before your users do. And if the thing you want to build does not need AI to work well, I will tell you that on the call.
Full-Stack Web Development
Websites and web applications built to production standards.
Not every project is a SaaS product. Sometimes you need a high-performance marketing site that converts, a company website built for SEO, a custom web application that replaces a manual process, or a client portal that doesn't look like it was made in 2014. I build these with the same production-grade stack: Next.js, Tailwind, a CMS your team can actually use, and deployment that won't break when you share it on LinkedIn.
Match your situation to the right engagement.
Not sure what the product needs next, and want a clear picture first
TECHNICAL ASSESSMENT →Inherited a codebase, or weighing a rewrite or a technical acquisition
TECHNICAL ASSESSMENT →Live product with paying customers, and the team needs a senior engineer who owns it
SAAS ENGINEERING PARTNERSHIP →Building a new B2B SaaS product from zero
SAAS PRODUCT BUILD →Have a Lovable / Cursor / v0 prototype that needs to go to production
AI PROTOTYPE RESCUE →Need RAG, agents, or AI features built inside an existing product
AI DEVELOPMENT →Not sure? Book an intro call and I'll tell you which engagement fits.
Same scaffolding. Every engagement.
Assessment first
Every engagement starts with a one-week Technical Assessment: what the product needs, what that takes, and a written plan you keep either way. The fee is credited toward follow-on work.
Weekly updates
Every Friday: what shipped, what is next, and the decisions made along the way. You always know where the product stands.
I stay responsible
I own the outcome, not just the tickets. Everything is documented, so your team can keep building on it with or without me.
Six years of shipping.
I don't take on work I can't deliver.
If something isn't realistic for your product, I'll tell you on the intro call or in the assessment, not halfway through the build.
Questions founders actually ask.
With a paid technical assessment. I look at what you have (or what you want to build), tell you what it actually needs and what that takes, and you keep the plan whether we work together afterwards or not. The fee is credited in full toward any follow-on engagement.
Building, growing, or maintaining a SaaS? Let's talk.
A short intro call first. If it is a fit, we start with a one-week Technical Assessment, and the plan is yours to keep either way.