Your project, week by week.
Pick the kind of project you have. The steps below fill in with what happens, what you receive and what we ask of your time.
What building an app with us looks like
From the first call to an app your users can open, with working software to see every week.
- At the start
Requirement call and written proposal
What happens
We talk about who will use the app and what it must do. Then we write down the scope, the timeline and the quote.
What you receive
A written proposal. You pay nothing until you agree.
Your time: A call, then reading the proposal
- Before the build
Clickable screens you approve
What happens
We draw every screen and link them, so you can tap through the app before it is built.
What you receive
Clickable screens for you to approve in writing.
Your time: Tapping through the screens and approving them
- Every week
Build with weekly demos
What happens
We build the app in small pieces. Every week you see the working app, not slides.
What you receive
A weekly demo and a short written update.
Your time: The weekly demo and a reply to the update
- At the end
Test, launch and train
What happens
We test the app, take it live and train your team. Monitoring, tests and human checks come with it.
What you receive
The live app, with the code, accounts and documentation handed to you. 30 days of free fixes.
Your time: A last check and a short training for your team
- After launch
Monthly care
What happens
We watch the app, fix problems and make small updates every month.
What you receive
A simple monthly report.
Your time: Reading the monthly report
These steps are a guide. Your written proposal sets the real timeline, and you agree to it before we start.
Every build week has the same three beats.
A goal at the start of the week. Working software in the middle. A written update at the end. Choose a beat to see what it looks like.
The week starts with a goal, agreed in writing.
Before we build anything this week, we write down what you will be able to do by the end of it, and what is not in this week. You say yes, or ask for a change. Then we start.
The goal is small enough to finish in one week.
- Customers can sign in and see their orders.
- It works on a phone.
- Not in this week: payments.
Agreed by you in writing before the week starts
Which way fits you?
Answer three questions. We suggest one way, in plain words.
Do you know exactly what you want built?
Is it live already and needs looking after?
Do you want engineers inside your own team?
- ProjectA scope, a timeline and a quote. You approve, we build.
- Monthly care planWe look after software that is already live.
- Dedicated developersOur engineers work inside your team, month by month.
- AssessmentA short look first, when you are not sure what to build.
Answer the three questions and your suggestion appears here.
What we ask of you
- One person who can say yes or no.A quick answer keeps the weeks moving. We ask for quick replies, and your proposal says how quick.
- A short call at the start, and the weekly demo.That is the time shown on every step card above.
- Real examples from your work.A sample invoice, a screenshot, the spreadsheet you use today. They teach us faster than a description.
- Your approval in writing.A message is enough. We do not start the next step without it.
- Your words and pictures, if you want them used.Logo, photos, text. We tell you early what we need and by when.
What stays yours
- The code, the accounts and the documentation.They belong to you. We hand them over.
- Your data.We follow India’s data protection law (DPDP), sign a data processing agreement, and can keep your data in the country or region we agree in writing, such as India. If other rules apply to you, we set out in writing what we do for each.
- Your secrets.We sign a non-disclosure agreement (NDA) on request, before you share anything private.
- The final say on scope.Nothing is added or dropped without your written approval.
Nothing moves until you say yes.
Plans change. That is normal. Here is what happens when yours does.
You tell us
Send the change in your own words. A message is enough.
We write what it does to time
In plain words, we write down what the change does to your timeline and your quote.
You approve before we do it
We start the change only after you say yes in writing. If you say no, the plan stays as it was.
You wrote“Can the app also send a reminder on WhatsApp?”
What it does to timeIt adds some days to the timeline. We write down how many.
What it does to the quoteWe write down the extra cost, if there is any.
Nothing starts until you answer below.
Your answer, in writing:
Questions about the working side
Did not find your answer? Ask us in the requirement form.
How does a project start?
You send your requirement through the form. A senior engineer reads it and replies within 1 working day. After a call, we write a proposal with the scope (what is in and what is not), the timeline and the quote. You pay nothing until you agree.
How will we stay in touch?
Every week you get a demo of working software and a short written update. How we reach each other for quick questions is agreed with you in writing before we start.
How fast do you reply?
A new requirement gets a reply within 1 working day. During a project, the reply time for your questions is written in your proposal.
Who will I talk to?
Senior engineers build your project. Your proposal names the person you talk to.
How often will I see progress?
Every week. You see working software in a demo, and you get a short written update: what is done, what is next, what is blocked and what we need from you.
What happens if I stop?
The code, accounts and documentation are yours. How the work done so far is billed and handed over if you stop part-way is agreed in writing before we start.
Pick your project. We will write your weeks.
Send your requirement. We reply within 1 working day. After a call, you get a written proposal with the scope, the timeline and the quote. You pay nothing until you agree.