Process
From clicking around to going live.
No discovery retainer and no six-month implementation. Five steps, a fixed price, and a date we are willing to commit to.
01
Click through the real thing
Every app in the catalogue is deployed and running. You open it, move a deal, receive stock, approve a claim. No sales call stands between you and the software, and nothing you see in a demo is a screenshot.
02
Tell us what is different about you
One call, about an hour. We map your stages, your approval thresholds, your document numbering and the two integrations that matter. You leave with a written scope and a fixed price for the changes, not a discovery retainer.
03
We fit it to your process
Typically one to three weeks. Fields, rules, roles, branding and the integrations agreed in scope. You see it on a staging URL from day two and comment as it goes, rather than reviewing at the end.
04
Migration and go-live
We move your existing records in, run both systems in parallel for a week, and train the team on the screens they will actually use. Go-live is a scheduled event with a rollback plan, not a hopeful Friday.
05
You own it
Full source code, in your repository, under your cloud account. Twelve months of updates are included. After that, keep it yourself, hire anyone, or keep us on, the choice stays open because the code is genuinely yours.
Timeline
One to three weeks, and you know which.
The scoping call ends with a fixed price and a date. We would rather lose the work than agree to a date we do not believe.
Week one
Scope signed, environment provisioned, branding and data model adjusted. Staging URL live by day two.
Week two
Workflow rules, roles and integrations. Your team comments on staging while it is being built, not after.
Week three
Migration rehearsal, reconciliation against your current totals, training, then a scheduled cutover with rollback.
Mobile
Shipping to an app store adds a step.
The five steps above describe a web build, where go-live is a deploy you control and you can ship a fix the same afternoon. An on-demand mobile app has two gatekeepers in front of it, and they change the rhythm rather than the process.
Store accounts, in your name
You open the Apple and Google developer accounts before the build starts and hold them throughout. We publish from them; we never hold them. If we part company the listing, the reviews and the install base stay with you.
Review before every release
The first submission and every update afterwards is reviewed before it reaches users, usually days, occasionally a rejection and a resubmission. We handle both during the build. It means batching changes into releases rather than shipping daily.
Start by clicking through the software
Every app in the catalogue is live with sample data. Open one, use it properly, and decide afterwards whether it is worth a conversation.