You can deliver a working client app in a week by splitting the work into five steps: discovery and a first build live on the call, revisions with the owner, a check with the people who will use it, staff onboarding, and launch on the client's domain. The first version takes minutes with an AI app builder like Alori. The rest of the week goes to making it fit the business and getting the team comfortable with it.
What "done in a week" means
Set the target clearly with the client. By the end of the week:
- The app holds their customers, quotes, schedule, jobs and invoices, using their words.
- The office and field staff have logins and know how to do their daily tasks.
- The app is live on the client's own domain or a name.alori.dev address.
- There is a list of next improvements for the following weeks.
It does not mean every wish is built. A focused first version that the team actually uses beats a perfect one that launches in three months.
The week at a glance
| Day | Goal | Who is involved |
|---|---|---|
| Monday | Discovery and first build live on the call | You and the owner |
| Tuesday | First round of revisions | You, owner on a short call |
| Wednesday | Walkthrough with daily users, second round of revisions | You, office manager, a crew lead |
| Thursday | Staff onboarding | You and the whole team |
| Friday | Launch on their domain, first-day support | You, owner |
Adjust the days to the client's schedule. Some trades are hard to reach in the morning; book calls around their work.
Monday: discovery and a first build on the call
Book 60 to 90 minutes with the owner.
- Discovery (30 minutes). Follow one real job from first call to paid invoice. Use the questions in discovery call questions for service businesses.
- Build it live (15 minutes). Paste their website into Alori so it picks up the business name, colors and what they do. Add a few sentences from your notes. Answer the multiple-choice questions Alori asks instead of guessing.
- Walk through it together (20 minutes). Open their customers, create a quote, turn it into a job, look at the schedule, make an invoice.
- Make one change live. Ask the owner what is missing and type the request. Seeing it appear builds trust fast.
Before you hang up, write down the top five changes and confirm who should join Wednesday's walkthrough. Also ask who controls their domain, so Friday has no surprises.
Tuesday: first round of revisions
Work through Monday's list alone, then show the owner in a short call.
Typical first-round changes:
- Renaming things to match their words ("visits" instead of "jobs").
- Adding fields they need on every customer or job, like gate codes or equipment type.
- Adjusting how quotes are built for their pricing.
- A simple report, like jobs done but not yet invoiced.
Each change is a sentence. In Alori, changes are tried on a copy of the app first, so you can experiment freely and only publish what works. Keep changes small and check each one before moving on.
Wednesday: walkthrough with daily users
The owner often isn't the main daily user. The office manager and crew leads are. Book 45 minutes with them.
- Let them drive. Ask them to enter a real customer, book a real job and send a test invoice.
- Watch where they hesitate. That is where the app needs to be clearer.
- Have a crew lead open the app on their phone and find today's jobs.
Make the second round of changes that afternoon. Keep a "later" list for anything that isn't needed on day one. Scope creep is the main thing that turns a one-week launch into a one-month one.
Thursday: staff onboarding
Invite the client's staff into their project. Each Alori project is a separate app with its own data and its own team, so they see only their company's app.
A simple onboarding plan:
| Group | Session length | What they learn |
|---|---|---|
| Office staff | 45 minutes | Customers, quotes, scheduling, invoices |
| Crew leads and technicians | 20 minutes | Logging in on the phone, today's jobs, notes, marking work done |
| Owner | 15 minutes | Reports, how to request changes from you |
Tips:
- Train on their real data, not samples.
- Give each group a one-page cheat sheet with their three most common tasks.
- Tell them who to call with questions. That should be you.
Friday: launch
Publish the final version and put it on the client's domain, or on name.alori.dev if they prefer. Alori handles hosting, the database, sign-in and SSL, so launch day is about people, not servers.
On launch day:
- Check that every staff member can log in.
- Stay reachable all day for questions.
- Send the owner a short summary: what is live, what is on the "later" list, how to request changes.
Since you can go back to an earlier version at any time, a mistake in the launch build is easy to undo. That makes a Friday launch less risky than it sounds.
The week after
Launch is the start of the relationship, not the end.
- Check in after two or three days and again after a week.
- Work through the "later" list in small batches.
- Set up the monthly rhythm for changes and support.
See maintaining client apps for the ongoing routine, and how to price custom apps for clients for how to charge for it.
Frequently asked questions
Can a custom business app really be built in a week?
A focused first version can. The build itself is fast with an AI app builder; most of the week goes to revisions, training and launch. Keep the scope to what the team needs on day one and add the rest afterward.
What if the client is too busy for daily calls?
Combine days. Monday and Wednesday are the most important sessions, since they cover discovery and real users. Tuesday's revisions can be shared as a link with a short note instead of a call.
Should the client move all their old data before launch?
Start with what the team needs right away, like active customers and upcoming jobs. Entering those during training doubles as practice. Older history can stay in the old tool for reference until the new app has settled in.
What happens if staff push back on the new app?
Involve them early, as in the Wednesday walkthrough, and make the changes they ask for. People adopt tools that use their words and match their routine. Keep the first version simple so there is less to learn.
Run your first one-week delivery
Pick a client, book the Monday call and build the first version with them. Alori is free to start, with no credit card and no account needed to try. Start a project.
