Will I actually have a product I can charge money for?
+
Yes. You get a live product on your own domain with working payments — real customers can sign up
and pay from day one, not click through a demo. It's the same approach that's already live and
earning on
dst.travel
and
WarmLane.
What do I actually walk away with?
+
A production product running on your own server and domain — plus the complete source code, IP
transfer, and documentation (requirements, code & feature docs, the tech choices and why, and a
deployment guide). It's fully yours: hire any developer to extend it, with zero lock-in to me.
What if I need it in less than 30 days?
+
Possible for tighter scopes. We discuss timeline trade-offs on the discovery call — if a 14- or
21-day build is realistic for your scope, I'll say so honestly. If not, I'll tell you the same.
What if my project is bigger than $10K scope?
+
Most projects fit in $10K if scoped well. For larger projects, we discuss phased delivery —
phase 1 ships in 30 days, additional phases priced separately. You get a working MVP first,
then expand.
Some of your projects took longer than 30 days — why?
+
Because the client chose to add more — not because the build slipped. The 30-day timeline covers
the agreed MVP scope. Once a client sees the product taking shape, they often want extra features:
that's exactly what happened with WarmLane, which grew into a full multi-tenant platform over
~6 weeks. Those additions are agreed upfront and priced separately, and the codebase is
deliberately built to be extended, so adding on is clean rather than a rewrite. The goal never
changes: get your core product to production as fast as possible, then grow it from a live,
revenue-ready base — not a half-finished one.
Do you only build AI products?
+
No. AI is my sweet spot — but the same 30-day timeline applies to non-AI products too. Internal
tools, SaaS dashboards, marketplaces, admin systems — anything that benefits from senior solo
engineering. AI-assisted development is the leverage I use to build fast; it's not a requirement
for your product.
What about ongoing maintenance after launch?
+
60 days of post-launch support included free — covers bug fixes, deployment issues, and minor
adjustments. New features and scope additions move to an optional technical retainer
($1,000–$3,000/month depending on scope, or $50/hour on-demand). Or take it fully in-house with
full source code + documentation provided.
Can you sign an NDA before we talk?
+
Absolutely. Mutual NDA signed before any technical discussion. I can send my standard mutual
NDA, or sign yours.
What does the discovery call actually cover?
+
30 minutes. You describe what you're building, your deadline, and budget. I tell you honestly
whether I'm a fit. If yes, I follow up with a 1-page scope + proposal within 24 hours. No
pressure, no prep needed.
Why fixed price, not hourly?
+
Fixed price aligns incentives. You know your total cost upfront; I'm motivated to ship
efficiently, not bill more hours. We both win when the project ships fast.
Do I own the code? Am I locked into working with you?
+
You own everything — full source code, IP, and complete documentation, transferred to you. That
includes a requirements doc, code & feature documentation, the technologies used and why, and
a deployment guide covering how and where it's deployed. Any developer can pick it up and extend
it. You're never locked into me — hire your own team or scale in-house whenever you want.
Can I see code from past projects?
+
After NDA. Happy to do a live code walkthrough on the discovery call for serious prospects.
DST.Travel is the most recent public example — see the case study page or watch the Loom
walkthrough above.
What if the project goes over 30 days?
+
Rare — but if scope shifts or new requirements emerge mid-build, we discuss together. Either
we de-scope to keep the deadline, or we agree on a brief extension. No silent timeline creep.
