Overview¶
flowchart TD
P1["Free Consult"] --> P2["Demo deck"]
P2 --> P3["Sign and Pay Deposit"]
P3 --> P4["Work begins"]
P4 --> P5["Iterate on sprints"]
P5 --> P6["Pay the remainder"]
P6 --> P7["Handoff"]
%% Each box links to the section it names, further down this page. Mermaid
%% wraps the node in <a xlink:href> and sanitises the URL, which a bare
%% "#anchor" passes, so this needs no `securityLevel: loose` -- and we do
%% not want that anyway: loose switches off the DOMPurify pass over the
%% whole diagram. The section titles are the ids these point at, so a
%% renamed heading silently breaks the box that named it.
click P1 href "#free-consult" "Free Consult"
click P2 href "#demo-deck" "Demo deck"
click P3 href "#sign-and-pay-deposit" "Sign and Pay Deposit"
click P4 href "#work-begins" "Work begins"
click P5 href "#iterate-on-sprints" "Iterate on sprints"
click P6 href "#pay-the-remainder" "Pay the remainder"
click P7 href "#handoff" "Handoff"Free Consult¶
This is the planning part. Before anything is built, we agree on the exact problem you want solved, and on what the finished product needs to do.
flowchart TD
A["Request a Free Consult"] --> B["Describe the problem"]
B --> C["Name 3 screens to solve it"]
C --> D["Link 3 websites with a<br/>desirable interface for each<br/>screen listed above"]
D --> E["A beautiful solution,<br/>agreed before any code, in a working Demo deck"]Demo deck¶
Once you start, we set up a real, working prototype of your app. Not a drawing of one you can only look at, but something you can click through and use. It runs on the free plan of a hosting company, and the screens are live on the internet. You get a short slide deck as well, and the deck holds that working prototype inside it, so when you show it to someone they can use the product instead of hearing about it.
The prototype is not open to anyone. It sits behind a sign-in screen, which is what lets you show it to a client, an investor or a colleague without putting it on the open internet. Anyone who has not been invited simply cannot get in, so nobody is left staring at a login page or a link that goes nowhere.
The last part of the deck is a statement of work (SOW): a short document saying what will be built, in what order, and what each round of work costs.
flowchart TD
A["Workflow triggered<br/>to create the Demo deck"] --> B["Provision on the free tier<br/>of a cloud provider"]
B --> C["Static hosting for the 3 screens"]
B --> D["Gateway for access control"]
C --> E["Prototype live at a private URL"]
D --> E
D --> F["Sign-in required:<br/>only invited accounts get in"]The slides explain why your business needs this in the first place. You can email the deck to whoever you like, and they can read it without signing in.
flowchart TD
G["Generate the demo deck"] --> H["Slide 1: the problem, and the solution"]
H --> K["Slide 2: the live embedded prototype"]
K --> I["Slide 3: explain deploy it anywhere"]
G --> M["Slide 4: the statement of work with how many sprints and cost per sprint"]
M --> N["Slide 5: select a follow up date from a calendar, and enter your feedback, and click submit feedback"]
N --> L["Slide 6: thank you slide with a link to sign and pay deposit to start SOW"]
The final slide is the point of the whole deck. It is there to walk you to the point where you are ready to sign the SOW and pay your deposit. Every slide before it exists to show you what you get once the work starts.
Sign and Pay deposit¶
The prototype stays locked until the deposit is paid. That deposit is what gets the project moving, and the remaining balance is due at the end.
flowchart TD
A["SOW reviewed in the deck"] --> B["Sign and Pay Deposit"]
B --> C["Deposit clears"]
C --> D["Work begins"]Work begins¶
Once the deposit clears, we switch your access on and add you to the prototype as an admin, which means full access to everything behind that sign-in screen. You are added to the system itself rather than handed a link and a login form, and that is what stops anyone else wandering in while the work is still unfinished.
flowchart TD
A["Deposit cleared"] --> B["Customer's account<br/>added to the allowlist"]
B --> C["Role: admin"]
C --> D["Customer signs in at the gate"]
D --> E["Tests the real system:<br/>every screen, every edge case"]
E --> F["Feedback goes into the SOW backlog"]Iterate on sprints¶
The work moves in short, fixed rounds. Each round is called a sprint, and the estimate in the SOW is simply a count of them, so you always know what you are paying for and what comes next.
flowchart LR
S["Sprint day"] --> R["Review day"]
R --> D{"Scope complete?"}
D -->|"No"| S
D -->|"Yes"| F["Ready for the final payment"]Pay the remainder¶
The last payment is the second gate. Once it clears, handoff is unlocked: you can copy the whole project into an account you own.
flowchart TD
A["All sprints signed off"] --> B["Customer pays remainder"]
B --> C["Payment clears & Handoff"]Handoff¶
The project ends up yours. You have a license to use it as you see fit and We do not hand you a login for something running on our accounts. We hand over the whole software repository source to clone, and where you run it is your choice: a hosting company, a server you already own, or a small device such as a Raspberry Pi.
flowchart TD
A["Handoff"] --> B["The stack is yours. <br>Host it 0% to 100% in <br> <u>5 minutes</u>"]
B --> C["Cloud Hosting <br> <u>$0/month</u> <br> (free tier, then pay by use) <br>Deploy to a cloud provider with a generous free tier"]
B --> D["VPS Hosting <br> <u>$5/month</u> <br> Host with any hosting company, no vendor lock in"]
B --> E["Self Hosting <br> <u>Your hardware (freeish)</u> <br>Run online, offline, or in mission critical fields where you need to own the hardware"]
C --> F["Full ownership"]
D --> F
E --> F