Engagements

Fixed price. Fixed scope. A definition of done.

No hourly billing, no scope drift and no invoice you did not see coming. One number is published here — the teardown — because every other number should come out of a diagnosis rather than a guess. 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

Fixed price, set from the teardown

Agreed in writing before any work starts.

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

Fixed price, set from a scoping week

Agreed in writing before any work starts.

An idea becomes a live product. Scoped, built and deployed by someone who has taken this across before.

What you get

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

Why one number

A price before a diagnosis is a guess.

The teardown is priced here because it is the same five days whatever I find. Everything after it depends on what the five days turn up, and a number quoted before that is either padded against the unknown or quietly wrong — and you pay for both.

So the sequence is deliberate. Buy the diagnosis, read the findings, and get a fixed price for the work it identifies. You are free to stop there, take the document to someone else, or do none of it. Nothing after the teardown is quoted until there is something real to quote against.

What you will never get is an hourly rate and an estimate. The number is fixed before work starts, and if I have misjudged the effort that is mine to absorb.

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.

Priced per engagement

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.
Who actually does the work?
I do. That is usually the reason to hire this rather than an agency, where the person who sold the work is rarely the person who builds it. What sits around it is ordinary company machinery rather than a handshake: Layap Infotech Pvt. Ltd. contracts and invoices, every engagement runs under a signed statement of work with an explicit definition of done and a change-control route, defects are re-performed at my cost, and the handover is only accepted once one of your own engineers has deployed and restored the system from the written material. Where a piece of work needs a specialist I am not, that person is named and approved in writing before they touch anything.
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