Engagements

Fixed price. Fixed scope. A definition of done.

No hourly billing, no scope drift and no invoice you did not see coming. Prices are quoted in USD, with the Indian equivalent alongside. Exclusive of GST, invoiced by Layap Infotech Pvt. Ltd.

Teardown

5 days

$500

₹40,000 in India · ex-GST

Why your project has not shipped — written down, ranked by severity, with what it takes to cross.

What you get

  • Architecture and code review
  • Severity-ranked findings document
  • What is actually blocking production
  • Scoped plan to get there
  • 90-minute walkthrough call

Most asked for

Crossing sprint

3–4 weeks

$6,500

₹5,50,000 in India · ex-GST

Your prototype becomes a system people can depend on. This is the gap most projects die in.

What you get

  • Auth, tenancy and access control
  • Evaluations, guardrails and cost ceilings
  • Observability, alerting and error handling
  • Deployment, rollback and runbook
  • Handover to your team

0→1 sprint

6 weeks

$11,500

₹9,50,000 in India · ex-GST

An idea becomes a live product. Scoped, built and deployed by one person who has done it three times.

What you get

  • Scope, data model and architecture
  • Production build, front to back
  • Deployment and infrastructure
  • Instrumentation from day one
  • Source, documentation and handover

Ongoing arrangements

For companies that need the capability continuously rather than once.

Agency build arm

Your clients are asking for work you cannot staff. I build it under your name, to your deadlines.

from $2,400

from ₹2,00,000 / month

Fractional CTO / Head of Product

Two days a week of senior product and engineering judgement, for a company that needs it before it can hire it.

from $3,000

from ₹2,50,000 / month

Questions people actually ask

I already have engineers. What do you actually do?
Most teams that cannot get a project into production are not short of engineers — they are short of someone who has taken this particular kind of system across before and knows which of the twenty remaining problems are the three that matter. I work alongside your team, not instead of it, and everything I build is handed over with the source and the reasoning.
What if the teardown concludes the project should be killed?
Then it says so, in writing, with the reasoning. That is a useful answer and it is cheaper to buy than another two quarters of engineering. I would rather lose the follow-on work than write a document that tells you what you hoped to hear.
Isn't this just AI writing the code?
AI writes drafts. Deciding which draft is correct is the work, and that is the part that did not get cheaper — there is simply more plausible-looking output to be wrong about now than there used to be. Every failure mode I have measured is on the how-I-work page with the number attached, because the specific version of that answer is more reassuring than the comfortable one. What reaches you has been through a person who could have written it unaided, carries a fixed price I absorb if I misjudged it, and ends in a handover your own engineer performs while I watch. Nobody underwrites generated output on those terms without having checked it.
You are one person. What happens if you are unavailable?
Everything is handed over as it is built rather than at the end — source, infrastructure, and the reasoning behind the decisions — so at any point in a sprint you are holding something your own team can carry forward. Nothing depends on me being reachable, by design, because a dependency on one person is the same risk you are asking me about. And for a programme that genuinely needs a team of eight for a year, I am the wrong shape and will tell you that in the first conversation rather than the fourth month.
Do you work for equity instead of fees?
No. Fixed fees, invoiced by Layap Infotech Pvt. Ltd. Equity conversations are a different relationship and mixing the two makes both worse.
What is explicitly not included?
Ongoing feature development, design work beyond what the build needs, and staffing. If a sprint uncovers work beyond the agreed scope it gets written down and quoted separately rather than absorbed silently or billed as a surprise.
How quickly can you start?
A teardown usually starts within a week. A sprint depends on what is already committed — ask and I will tell you the honest date rather than the one you want to hear.
Where are you and which hours do you work?
Gurugram, India. I have worked with teams across US and European hours for over a decade; overlap is a scheduling problem, not an obstacle.
Start with a teardown