Step 01
Fill the brief
Ten questions about goals, constraints and what exists today. Short answers are fine.
- What should change, and by when
- Your current stack and data
- One number that means success
Process · H2M
A free call, a written plan, then the build
Three steps. The call costs nothing. The plan costs $1,250 and comes off the first invoice if we build together; if we do not, the documents are yours to take to anyone. Nothing is built before you have a date in writing.
The three steps
The same three on every service page and every lander.
- 01
Scoping call
30 min, freeYou describe the situation; I ask three questions and propose a shape.
- 02
Roadmap and architecture
$1,250 depositA written plan with a date. The deposit is credited to the first invoice; the documents are yours either way.
- 03
Build, handoff, operate
date on the roadmapOne engineer builds every layer on your account, documents it, and can keep operating it.
The deposit, in writing
What the $1,250 buys, and when it comes back
What you get for it
A written roadmap with a date and a fixed price for the build, and an architecture of your system on one page: what runs where, on which of your accounts, and what it costs to operate.
When it is asked for
After the scoping call, never before it. The call is free and ends with three questions and a proposed shape; you decide on the deposit once you have heard it.
If we build together
The full $1,250 comes off the first invoice of the build. The roadmap was the first piece of the work, so you do not pay for it twice.
If we do not
The roadmap and the architecture are yours to keep and to hand to any engineer or agency. No licence and no lock-in.
How it is paid
By card on a Stripe Checkout page, or by bank transfer against an invoice from H2M sp. z o.o. Card details go to Stripe and never reach this site. Privacy notice
Process · 01 / 06
From brief to roadmap
Six short steps, about twenty minutes of your time. The first is a free 30-minute call; the deposit comes after it and is credited to your first invoice.
- 01Fill the brief5 min
- 02Record a video request3 min
- 03Add attachments2 min
- 04Leave contact details1 min
- 05Pick a call slot1 min
- 06Pay the deposit2 min
Step 02
Record a video request
Optional. Voice or camera, up to three minutes, if that is easier than typing. Say it the way you would say it to me over coffee.
- Voice or camera, your choice
- Up to three minutes
- Only I see it
Step 03
Add attachments
Documents, screenshots, exports. They go straight into a private bucket, nowhere else.
- Drop anything in
- Private storage, no public link
- Deleted with the request
Step 04
Leave contact details
An email and a phone number. One consent for the one reply that matters.
- Phone
- Consent to be contacted
Step 05
Pick a call slot
Propose up to three times that suit you and confirm the number. I call you, not the other way round.
- Up to three times, your choice
- In your own time zone
- Confirm the number
Step 06
Pay the deposit
After the call: $1,250 funds the roadmap and the architecture. If we go ahead, it becomes a discount on the build.
- Roadmap and architecture, in writing
- Yours to keep, whatever you decide
- Credited in full when we start
Scroll
What stays with you
Yours from day one
- The repository on your GitHub account
- The Cloudflare account and the domains under your company
- The roadmap and the architecture, whatever you decide
- Handoff documentation, and an optional operation retainer
Questions about the process
Tap a question. The answer comes back like a text.
Scoping calls · most weeks
A written roadmap and an architecture for your system, delivered after the scoping call. If we build together, the full amount comes off the first invoice. If not, the documents are yours to take to anyone.
The roadmap gives you a date before you commit to the build. The stack is small and one person builds every layer, so nothing waits in a queue between departments.
You do. The repository, the Cloudflare account, the domains and the data sit under your company from day one. I get access, not ownership.
The system keeps running on Cloudflare with no servers to babysit. You can operate it yourself, keep me on for changes, or hand it to another engineer with the docs I leave behind.
Yes, on a monthly retainer with scheduled tasks that leave proof of their last run, so you can see the system is alive without asking me.
Yes, before you send the brief if you need it. Send yours or use mine.
Something else? Ask it on the call
A 30-minute call, free
Thirty minutes, then a written plan
Leave an email. I reply within one working day with three questions and a proposed plan, not a deck.