For developers and freelancers who can already build
A practical guide to structuring, pricing and delivering custom business software as a monthly subscription — built around one real project that earns every month, with its unknowns stated as unknowns.


13 editable tools
+ 20 AI prompts
One-time purchase. Not a subscription. You are charged once.
The case study
One project anchors this book. Here is exactly what is true about it, and exactly what is not — stated the same way on this page as it is inside the book.
Verified
$500
per month — the subscription price of one real system, for one client
Not claimed, anywhere
Chapter 2 lists the same six facts and then spends the rest of the chapter on what they do not prove. Chapter 5 uses a competitor pricing screenshot, labelled as an undated observation, without naming the vendor or claiming the products are equivalent. Every worked number elsewhere in the book sits inside a block marked Illustrative.
Fit check
Outcomes
Not "what you will learn". Six documents that did not exist before you started, each one produced by a chapter and a worksheet.
One paragraph, in the client's words and their numbers, that they have read and agreed with before you write anything else.
An in-scope list capped at twelve items, and an out-of-scope list that is deliberately longer. The second one is what prevents the argument in month five.
Built from your build hours, your hosting, your third-party per-unit costs and your support time — not from a competitor's pricing page.
Two pages, with a structure that makes the decision easy for someone who is not a developer. Plus a filled example so you can see the tone.
Onboarding, the five support answers, backups you have actually restored, and the change-request process — written down before you need them.
Acquisition experiments with a cost, a signal and a stop rule, and dates in a tracker. Not a wish list.
The book
16 chapters, about 60 pages, in both editions. Every chapter ends with something to decide, write or calculate.
These are screenshots of the actual exported PDFs, not mockups. The two editions carry the same chapters, examples, numbers and exercises; a build check fails if a table or a figure goes missing from either one.






The toolkit
Thirteen editable tools in plain Markdown and CSV, so they open in Excel, Google Sheets, Numbers, LibreOffice, Notion or Notepad — and nothing you write is trapped in a format you have to keep paying to open.
The full 45-minute script, with the probes for when they gloss over a step.
Four gates and a 0–3 scoring grid across six criteria.
One row per capability, with an Evidence column that forces "Unknown" when you cannot cite anything.
Nine sections, plus a completed illustrative example so the tone is visible.
The markup exercise, the cut test, and the out-of-scope list that has to be longer.
A minute-by-minute run sheet, the four objections, and what to write down while they talk.
Before launch, launch day, week one, week two, week four, and the 90-day re-price check.
Fault or change, impact, hours, and whether it adds a recurring cost.
The five support answers, a request log, and the escalations you decide in advance.
Nine lines, same day every month. Five minutes of work with the highest return in the book.
Six messages with notes on what to change and what to leave alone.
A row per day with dates, plus an experiment log with stop rules.
Subscription pricing calculator
Open it in a browser, type your own numbers, and it shows you what the deal really is. It runs entirely on your machine — there is not one network request in the file.
The prompt pack
Twenty copy-ready prompts covering the whole arc: evaluating a niche, preparing and analysing interviews, extracting requirements, comparing competitors from evidence you supply, scoping, modelling economics, proposals, outreach, follow-ups, demos, scope negotiation, change requests, technical planning, code review, documentation, onboarding, support triage, monthly reporting and portfolio case studies.
Each line is there because of a specific failure mode, explained in Chapter 14. Take them out and the model fills gaps silently and confidently, and you cannot tell which parts it invented.
RULES:
- Ask me for anything you need that I have not provided, before answering.
- Base your answer only on the information I have given you.
- Do not invent statistics, research, prices, benchmarks, vendor names or
citations. If you do not have a fact, write UNKNOWN.
- List every assumption you made in a separate section at the end,
labelled ASSUMPTIONS.
- Do not include any information that could identify my client.Pricing
A one-time payment. Not a subscription — nothing recurring is set up, and no card is stored.


Both the English and the Hinglish edition are included in the same purchase. You do not choose one; you get both.
Optional
The book is complete on its own — every chapter, both editions, the toolkit and the prompt pack. Nothing has been held back to sell you this. The one thing a book cannot do is look at your specific situation.
₹5,000 per month. Manual monthly renewal — no card is stored and nothing auto-charges.
A separate purchase. You do not need the book to take it, and buying the book does not oblige you to consider it.
The session structure above is settled. Two things are not: how many people can be taken on at once, and whether the book is included for someone who has not already bought it. Enrolment stays closed until both are decided, rather than opening with terms that might change in a month. If you want to be told when it opens, get in touch.
The author
Rajan
Full-stack developer
Rajan is a full-stack developer who builds custom business software. He built a transport management system for a freight company, sold as a $500 per month subscription with no separate upfront development fee, unlimited users and unlimited shipments, customised around that company's workflows.
That is one project, one client, and one price. It is not a track record, and this book does not present it as one. Where the book recommends a method, it says so. Where it runs numbers, they are invented and labelled. Where something is not known — build cost, margin, how long the payback took — it says that instead of filling the gap.
The reason to write a book this way is simple: you are going to make pricing decisions with real money based on what is in it, and a case study that flatters itself is worse than useless to you.
FAQ
No. The book and toolkit are a one-time purchase at ₹499. No card is stored, nothing recurring is created, and you will not be charged again. Coaching is a separate offer at ₹5,000 per month and is not part of this purchase.
₹499 · one-time
Sixteen chapters, thirteen worksheets, a working calculator, twenty prompts, in two languages. One payment.
Get it — ₹499One-time purchase. Not a subscription. You are charged once.