How Albitor builds an app from a paragraph

Kickoff is a customer onboarding tracker for a B2B software startup, built from a one-paragraph brief with the Startup look. These are the screens its author sees at each stage.

Step 1 of 5

Say what you need, then check what Albitor understood

Write it in your own words. Albitor names the app, reads the brief back as the journeys it plans to build, and lets you drop or edit any of them before anything is built.

Kickoff’s Blueprint listing the journeys it plans to build: Sign in to the workspace, See every account’s progress, and Triage the accounts at risk. Each has a short description and Edit and “This isn’t needed” buttons, with “Drop all” above. — The journeys Albitor read back from Kickoff’s brief, each one editable or droppable.

Step 2 of 5

Settle the questions, the layout and the look

Albitor asks what the brief didn’t say, offers layouts, and lets you pick a style. The style you pick brings its own standards. The blueprint keeps every decision.

The Blueprint’s Style choice with five options: Startup, Business, Consumer, GOV.UK and GDS Other. Startup is selected. The GOV.UK and GDS Other options say they apply the GDS standards and checks. — The Style choice, with Startup selected.

Step 3 of 5

Watch each journey become usable

The Workshop shows which journeys work, what is running, and stops to ask when it needs you.

The Workshop’s Journeys tab early in the build. The work is 21 planned parts, with filters showing 1 running, 0 needing you, 0 waiting and 4 done. Two journeys, Plan the week ahead and See every account’s progress, are each not started, 0 of 2 parts. — Kickoff’s Workshop early in the build: 21 planned parts, 1 running and 4 done.

Step 4 of 5

See it checked before it ships

Every part is checked against the standards that come with the plugins you chose. Every journey is walked on a preview, and a failed or unproven check holds the build and says why.

Kickoff’s Assurance verdict: “Ready to hand over, with 1 thing to know”, checked as an Internal Tool against WCAG 2.2 AA accessibility and OWASP security. Three results sit below it: all 9 journeys work, 1 standard could not be confirmed (10 met; could not be confirmed is not a pass), and no serious problems open. Buttons read “Open handover report” and “Download data (JSON)”. — Kickoff’s Assurance verdict. One standard could not be confirmed, so the page says so rather than counting it as a pass.

Step 5 of 5

Go live, and take the code with you

Push to live on your own infrastructure, or on Albitor. Export the whole codebase, CI and infrastructure, plus the blueprint and assurance pack, whenever you like.

How long it takes

Kickoff has nine user journeys. The app and its assurance checks were done in a few hours. Albitor asked one round of questions, and its author picked a layout and confirmed two assumptions.

Join the waitlist