Loading...
Loading...
How I Price
I don't publish a rate card because no two projects are the same. Here's how I actually structure engagements and what drives cost.
Every engagement starts with a discovery conversation, not a quote. I'd rather understand what you're building, who it's for, and what success looks like before talking numbers. From there, I match the work to one of three engagement models below and put together a detailed proposal: scope, timeline, and investment, no surprises.
Best for well-defined scopes with a clear finish line: an MVP, a specific feature set, a platform migration. I run discovery to nail down requirements, then propose a fixed cost and timeline against that scope. No renegotiating mid-flight for work that was agreed up front.
Best for ongoing development after launch: new features, iteration, maintenance, performance work. You get a consistent block of my engineering capacity every month without writing a new proposal for every change request.
Best for sustained, high-velocity build-outs where you need engineering embedded in your roadmap long-term. Think of it as an extension of your own team: me plus my agent crew, covering full-stack, AI, and DevOps as one unit.
What Affects Cost
A landing page and a multi-tenant SaaS platform aren't priced the same way. The number of user flows, the depth of business logic, and how much of the system needs custom design versus off-the-shelf patterns all move the number.
A relaxed 4-month build costs differently than the same scope compressed into 6 weeks. Compressed timelines mean longer days and heavier agent-assisted parallelism on my end, which changes the investment required.
Every project gets me, and the seniority doesn't vary. What changes is the intensity: how much of my agent crew a project needs, and whether the timeline calls for parallel workstreams. That calibration is a direct input to cost.
Greenfield builds are simpler than work that has to play nicely with legacy systems, third-party APIs, existing data models, or compliance requirements. I scope every integration point individually during discovery.
Get A Custom Quote
Tell me what you're building, and I'll tell you what it takes: scope, timeline, and investment.