One focused job
Choose action user needs to complete, not long feature wishlist.
APP · PRODUCT FIRST VERSIONS
Turn one product idea into an app people return to use.
Start with one clear job, one usable loop, and evidence from real users before adding more.
LIVE PUBLISHED APP
One clear jobAccountsPracticeProgressFeedback
Start with reason someone comes back.
First version should prove one useful repeat loop.
A reason to return
Save progress, history, or next useful step so app improves with use.
Real feedback early
Put usable version in front of people before building wider product.
Build smallest complete loop.
One useful path is easier to test than many unfinished screens.
Name user and job
Define who opens app and what they need to finish.
Map first loop
Connect start, action, result, saved state, and next return.
Build usable version
Use real content and real devices. Remove unclear steps.
Learn before widening
Watch what people use, miss, and repeat before adding features.
GrammarScout belongs in APP.
Learners return to practise, review mistakes, and continue progress. AI coaching is supporting capability, not second lane.
APP · PUBLIC LEARNING PRODUCT
GrammarScout
Lessons, practice modes, mistake review, progress, and assisted coaching form one learning loop.
Questions founders ask first.
Usually about scope, ownership, and what happens after launch day.
What does it cost?
Right now, ₹50,000 flat for our first five clients. After those five it returns to the usual starting price of ₹1,00,000. The monthly stays the same either way, from ₹2,000 to keep it running and fix what breaks, because that is real ongoing cost and cutting it would mean cutting the service. The build price is fixed in the quote before work starts. It is a real build with accounts, saved information and admin control, and it is priced like one. Smaller ideas are often better served by a system than an app — we will say so if that is true.
Why is the founding price lower?
Because we are new, and our first clients carry the risk of that. They give us real workflows to learn from, honest feedback while we build, and permission to show the finished work to the next buyer. That is worth paying for, so we pay for it with a lower build price. Five places, then it ends. If the software genuinely helps you, we would like an introduction — but the price does not depend on it.
How small should the first version be?
Small enough that one person can finish one useful action in it. If a learner can complete a lesson, or an admin can mark a payment received, you have something real to test. Everything else can wait for evidence.
How long until people can use it?
Six to ten weeks for a first usable version, depending on how many screens and how much saved information the first action needs.
Who owns what gets built?
You do, in full. The finished work hands over to you, and you can take it to another builder without asking permission.
Can it grow later, or do we rebuild?
It grows. The first version is deliberately narrow, not deliberately throwaway. Screens and records get added onto what is already working.
Do you keep it running after launch?
Yes, if you want that. Keeping it live and fixing what breaks is part of the monthly. New features are quoted separately, so growth is always your decision.
What should people return to use?
Send rough idea, current prototype, or one user problem.