Four phases, no surprises.
You always know what happens next.
The same person you start with is the one shipping, the one on the call, and the one still around a year later.
Start with a discovery callDiscovery
We map the business, not just the brief.
Before anything is designed, we sit down and work through who uses this, how money moves, what the operation actually does today, and what version one has to prove. Most of the value here is in what we decide not to build.
- A written scope: screens, features, and what is out of scope
- Architecture and technology decisions, explained in plain language
- A fixed price and a delivery timeline
- A roadmap for what comes after version one
- An hour or two of your time on a call
- Access to whoever knows the current process best
- Any existing designs, data, or systems we should work with
Build
Working software every week, not status reports.
Design comes first as clickable screens you approve, then we build. Every week there is something real on a staging link that you can open, click, and react to. Changes are cheapest when you catch them in week three, not week eleven.
- A private staging link, updated every week
- Direct access to Ahmed on WhatsApp, no ticket queue
- Clickable designs approved before code is written
- A weekly note on what shipped and what is next
- Feedback on each weekly demo, ideally within a couple of days
- Decisions when we hit a fork that only you can settle
- Content, logos, and accounts we need to launch
Launch
Tested, monitored, documented, and handed over properly.
Launch is a checklist, not an event. The app goes to the stores or the site goes live, monitoring is switched on, and you get the documentation and the credentials. Nobody is left guessing what runs where.
- Deployment to your accounts, under your ownership
- Monitoring and error alerts configured
- Documentation, runbooks, and the full source code
- Thirty days of fixes at no cost, then support begins
- Approval on the release candidate
- Your store, hosting, and domain accounts
- A short window for final review before we go live
Partner
We stay, because launch is the beginning.
Six months of support comes with every build: issues resolved, small adjustments made. Beyond that, most clients move to a monthly partnership where we keep shipping improvements and I stay involved in the technical decisions as the business grows.
- Six months of support from launch, included
- Continuous improvements on a monthly partnership
- Technical advice as the business changes
- The same person, still accountable
- A monthly check-in, thirty minutes is usually enough
- Your priorities, so we build what matters next
Five things that hold on every project.
Whatever we build and however long it takes, these do not move.
One contact
Ahmed, start to finish
Scope before work
Written and agreed first
Weekly demos
Real software, every week
You own it
Source code and accounts
6 months support
From your launch date
Let's build something
worth running.
Share a few details and Ahmed will get back to you within 24 hours on weekdays, by email or WhatsApp, with a clear next step.
