Web apps, and the back end behind them.
One job, in one browser app. The screens, logins, permissions and system connections, built around a written scope.
Software we built, and run ourselves.
Browser-based business apps: the screens, and the logins, permissions, databases and system connections behind them. A project starts with one workflow and a written scope.
Rooftop artistic rendition and the Mailroom product screen. Illustrative and demonstration content.
Rooftop
Dealership reporting with Pay Runs for sales commission.
Live at a Melbourne new-car dealership
Explore RooftopMailroom
Inbox triage and replies in your voice. Review or enable automatic sending.
Live
MailroomMore examples and screen sizes
Apps, built to order.
Each began as one job somebody was tired of doing by hand.
Overview
901 · Office fit-outJob details
- Client
- Sample client
- Sector
- Commercial fit-out
- Site address
- Withheld in this demo
- Project manager
- Project lead
- Tender due
- Sample programme
- Documents
- Job folder
- Tender value (ex GST)
- $1,200,000
- Contract
- Lump sum · $1,200,000
The job, its people and its documents in one workspace.
To-do
Open tasks · By personDocuments
901 · Office fit-outScreens, permissions, data and hosting.
A web app is more than its screens. These are the pieces we scope, build and look after.
The screens
your staff or customers use, on a computer and on a phone
Logins and permissions
so each person sees what they should
The database and the rules
behind it
Connections
to the systems you already run
Hosting
with who looks after what written into the proposal
Testing on real devices
and your real data before go-live
Common questions
How much does a web app cost?
It depends on the job. You get a written scope and a fixed price before any development starts, and nothing is built until you agree it.
Then build, test, release and handover. See how custom work runs
Can you take over an app someone else started?
We need to look at the code and how it is hosted before we can say. Then we tell you plainly what we can pick up and what would need rebuilding.
Who hosts it, and who owns it?
Hosting, support and ownership of custom code are written into the proposal before work starts. Your data stays yours.
How long does a build take?
It depends on the scope. The written scope sets out what is being built, and you see it working early and often rather than at the end.
What do you need from us to start?
A rough description of the problem is enough. You do not need a technical brief.
A browser app, including use on a phone
The apps described here run in a web browser, on a computer and on a phone. An app-store release is a separate requirement to discuss before scoping the work.
Who builds it
Mark designs and builds what we sell, writes the code and looks after the servers. Jordan leads the conversations with you. You deal with the two people doing the work, not an account manager.
Not sure what to build yet?
Most work starts with one defined problem. If its shape is still unclear, a Workflow Blueprint gives you a written plan for one workflow, for a fixed fee, that you can use whether or not we build it.
Tell us what the app needs to do.
A rough description is enough.
