Service 02 / 04 · Systems: architecture, build, operation · all services
One system instead of three vendors: site, CRM and automations on your accounts
Web products, internal apps and e-commerce shipped as one codebase on your own Cloudflare account, and kept running after launch.
A site, a CRM, the automations between them and the MCP server on top are one system, not four vendors. I design the architecture, build it on the edge (Workers, D1, R2), hand over the documentation, and can keep operating it on a retainer with scheduled tasks that leave proof of their last run.
This is the right call when
- 01
The site, the CRM and the automations come from three vendors and nobody owns the whole.
- 02
You need a product, an internal app or a configurator that has to be live before the quarter ends.
- 03
Something is running and nobody can say whether it ran last night.
What you get
What lands on your account
- Architecture on one page, then the system on your Cloudflare account
- Site, CRM, automations and the MCP server as one codebase
- Scheduled tasks that leave proof of their last run
- Handoff documentation and an optional operation retainer
How it runs
Three steps. The six-step version, with the brief and the video request, is on the home page.
- 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.
Case studies
The systems behind this service, with the numbers their owners cleared for publication.
SeecontainerpoolA Swiss brand with a 3D pool configurator; one pricing truth shared by the configurator and a partner API.
de-CH launch with factory GLB models; CMS in pl/en/de.
- 3
- languages
- 1
- pricing API for site and partners
AdcareMulti-tenant CMS plus agency and per-clinic CRM for a clinic marketing agency.
Workers, D1, MCP; every clinic on its own tenant.
- CMS + CRM
- one codebase
pozyskajpacjenta.plClinic SaaS shipped in under four weeks: custom hostnames, booking, CRM, Stripe. Zero paying users so far, published as-is.
The honest one: the build is sound, the market pull was not there. Published anyway.
- <4 wk
- from brief to production
- 0
- paying users, honestly
Runs on
Workers
Pages
Sqlite
Hono
Typescript
Astro
Stripe
Actions
Questions I get about this
Tap a question. The answer comes back like a text.
Scoping calls · most weeks
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.
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.
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.
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.