Web applications
Customer or staff software in the browser. A first production version, scoped tightly enough to ship, with the paths people actually take.
Applications
Software, built to be used.
This is the practice for when the application itself is the work. Alpha Fox designs and builds a defined release, then hands it over in a state your team can operate.
Internal tools
The replacement for a spreadsheet someone is afraid to break. Built around the job, not around a tour of features.
Integrations
Connections between systems you already pay for, so the same fact does not have to be typed twice.
What you leave with
The running application, the source, instructions for operating it, and a record of the decisions so the next change is not a mystery.
How a build moves
This is a making process. It is not a recommendation. If you still need to decide whether to build, that is consulting.
- Name the outcome
Who uses it, what “done” looks like for them, and what this first release will refuse to include.
- Shape the smallest real version
A release small enough to ship and complete enough that someone can do the job in it.
- Design the paths
Screens and flows for the work, reviewed against how people actually behave, not against a slide.
- Build in the open
Working software as the work proceeds. You see the product, not a status report about the product.
- Hand it over
Source, how to run it, and the decisions beside the code. Your team can carry the next change.