AvocadoStackWorkflow web apps
A workflow web app has accounts and a path through the work: who can see what, and what happens after someone clicks. Brochure sites stay on WordPress. Phone apps stay on iOS and Android. This build is Django when the rules and the admin are the product, and Next.js when the interface is.
When it is the job
- An internal tool with more than one role
- A login your customers use in the browser
- A process that currently lives in inboxes and spreadsheets
Included
- A written scope before build
- The core workflow, not a tour of empty screens
- Accounts, roles, and the data those roles need
- Django or Next.js, named in the scope, deployed into hosting in your name
Not included
- An iOS or Android app. Phone apps are their own build.
- A third framework because the first two feel ordinary
- A redesign of the whole company while the app is in progress
- Hosting bills, SMS credits, and other vendor fees
Handover
- The repository and a short map of how it is put together
- Admin access and a note on the first things to click
- A list of what is live, what is deferred, and who to call