Task map
Who logs in, what they are allowed to see, and the one path that must work on a phone.
App & software
An app is justified when people repeat a task: booking a slot, checking an order, or updating a record. We map that task, design the screens, and build a web app your staff can open in a browser. A phone-app store listing is only added when the browser version is not enough.
Who it is for
A straight fit check.
For an operation with a clear daily task and someone on your side who owns the data. A weak fit for a brochure, a menu, or a one-page campaign — those stay websites.
You leave with
- Task map
- Screen prototype
- Working web app
- Admin access and operating note
Included
What the work actually covers.
Screens
The few screens the task needs, in the same maroon and ivory system as the public site when it is your brand.
Build
Accounts, forms, and a database on your hosting. We name what is stored and who can export it.
Handover
An admin login, a short operating note, and a list of what a later change would touch.
How it runs
From the first conversation to the files.
-
01
Prove the task
We write the task in one paragraph. If it needs more than one product, we split the quote.
-
02
Prototype
Clickable screens before the database work, so a wrong flow is cheap to change.
-
03
Release
A small group uses it first. We fix what that week reveals, then open it to the rest.
Questions
Before you write to us.
Will it be on the App Store?
Only if the job needs it. Most internal tools should be a secure website. Store apps add review time and a second codebase.
Who owns the data?
You do. The database lives on hosting you control, and the handover includes how to export it.
Start with this
Tell us what you need from app & software.
Email, a phone call, or the form. The same team reads all three.