WEB APPS · NEW IDEAS AND PROTOTYPES

Build a web app that people can start using.

Start with one job people need to finish. Already have a prototype? Begin with an assessment of what works and what needs attention before agreeing further development. Based in India, open to remote projects worldwide.

GrammarScout home screen
LIVE PUBLISHED APP
One clear jobAccountsPracticeProgressFeedback

Where are you starting?

A new idea and a half-built app need different first steps. Choose the situation closest to yours.

01

A first web version

Name who will use it and the first action they need to finish. Agree the screens, saved information and access that action needs.

02

An existing prototype

Show what already works and where it gets stuck. Review code access, saved data and broken steps before deciding what to keep, fix or rebuild.

03

A place for customers or learners

Start with one journey: sign in, complete a task, then return to saved work or progress. Member access and learning products can begin with a small, agreed scope.

Build and test the first task from start to finish.

Test whether someone can finish the task before adding more screens. If an existing product already meets the need, start there.

01

Understand the starting point

Define the user and their task. For existing work, assess the code, accounts and current behaviour first. A prototype review comes before a completion quote.

02

Write down the first release

Agree screens, user access, saved records and any payment connection. Name exclusions and checks for success. This offer starts with a web app; App Store and Google Play releases need a separate assessment.

03

Build and test the whole action

Test the agreed path on real devices, including failed actions and what each user must not access. Show a working result before adding more.

04

Agree ownership and support

Agree code and account ownership, how to take a copy of records, and who runs each service. Set support and running-cost boundaries in writing, then use feedback to decide what comes next.

Try GrammarScout’s lessons and practice.

GrammarScout brings practice, mistake review and saved progress together. Try a lesson, review a mistake, or check your progress.

Questions founders ask first.

Usually about scope, ownership, and what happens after launch day.

01

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. Your monthly price and everything it includes stay the same for your first two years. After that, any change comes in writing 60 days ahead, with the reason, and nothing you already use is ever taken away. 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.

02

Why is the founding price lower?

We are new, and our first clients take a risk by choosing us. In return for the lower build price, they let us learn from their daily work, give feedback during the build, and allow us to show the finished work to future clients. The offer ends after five clients. We would welcome an introduction if the software helps you, but the price does not depend on one.

03

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. Decide what to add after people have tried it.

04

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.

05

Who owns what gets built?

Your finished custom work is handed over to you. The agreement names the code, accounts, files and records you receive, so another builder can take over. Third-party tools and components retain their own licences and service terms.

06

Can it grow later, or do we rebuild?

The first version is planned around the agreed next steps. Later changes still need a scope check. With an existing prototype, we assess what can be reused before recommending further work.

07

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.

08

What other running costs should I check?

Ask which hosting, storage, email, payment and AI services the app uses. The quote should state which charges are included, which are separate, who owns each account and what happens as usage grows.

What should your first version help someone do?

Describe the user, their task and what already exists. Add a public prototype link if you have one. Leave passwords and private customer records out.

Chat on WhatsApp