Product Build
Turn the idea into something people use every day.
You want something that runs day to day: a product for your customers, a SaaS or an internal system your team works with. We build it for real use: design, development, cloud, operations and handover to your team. All from one team, with one contact.
A product build is worth it when the system is used daily by your customers or your team and there's no off-the-shelf tool that fits.
- For whom
- For teams that want something in real use, whether for customers or in-house.
- Duration
- Weeks, not quarters
- Outcome
- Running system, design, cloud setup, documentation, handover
Proven in these projects
6 apps
out, plus the translation subscription. The monthly licence cost is gone
5 days
from start of build to live
whyraw: a headless Shopify storefront that feels like the camera
Everything that runs in a browser and lives in the cloud.
Web, cloud and AI are one discipline for us. So there's no handoff between "the designer", "the backend team" and "the AI people".
Web apps, SaaS and internal systems
Next.js, Node, Postgres, auth, billing, multi-tenancy. For your customers or for your own team, from the first user to day-to-day operation. If you need an app for iOS and Android, we build it with React Native from the same codebase.
Shops and e-commerce
Fast shops with fewer add-ons: we replace expensive extra tools with features in the shop itself, clear out unnecessary scripts and make load times and upkeep simple again. When the frontend is part of the brand, we build it separately.
AI automation and agents
Document pipelines, analysis, assistants and agents, connected to ERP, CRM and accounting. We pick the model and platform to fit the job. Where it matters, a person checks the result.
Design
Included, not an add-on. Visual identity, UI, interaction. What works well should look good too.
An early first version, then better step by step.
Scope
From the pilot or the call: what the first version must do, and what it deliberately won't do yet.
First version
Online and usable, usually after a few days. From then on you get real feedback instead of opinions.
Keep building
An update every week. You see every version live, not as a screenshot.
Handover
Documentation, monitoring, access and a runbook. Your team takes over, or we stay on as Fractional CTO.
Three things we don't negotiate.
Live early
No big bang at the end. The first version goes live early, and after that we improve a running system.
Boring where it counts
Proven technology, no experiments on load-bearing walls. Bold only where it makes the difference.
Everything with you
You get code, infrastructure, access and documentation.
What you can rely on.
Fixed amount
Before the start you get a fixed amount for the scope agreed in writing. We only charge more if you commission additional work. Third-party costs, such as hosting or AI, are listed separately in the offer.
Go-live commitment
We only go live after your acceptance. If something that worked at acceptance fails in the 30 days after, we fix it at no cost, unless someone else changed code, extensions or settings, or a provider outside our control is the cause.
For businesses only. The written offer sets out the details, and your statutory rights remain in place.
After go-live: operations and development.
If you like, we stay on after handover with a fixed monthly scope. Or your team takes over with our documentation.
- Updates and security fixes
- Monitoring and fixing incidents
- Small improvements from daily use
- One contact who knows the system
Common questions
How is it billed?
Flat fee, not by the hour. Before the start you get a written offer with scope and a fixed amount. How much it is depends on the scope and is clear after the first call.
Do we need a pilot first?
Not necessarily. If the requirements are clear, we start right away. If not, a 10-day pilot gets you clarity faster.
How long does a product build take?
Weeks, not quarters. A shop or a focused web app is often live within four to eight weeks. Larger products we plan in several releases.
Who runs the system afterwards?
Your team, with our documentation and a handover session. If you like, we stay on for operations or as Fractional CTO.
Do you work with our existing team?
Yes, together rather than side by side: shared pull requests, reviews and roadmap.
More on specific topics
Shopify
Shopify stores that load fast and don't depend on a pile of apps.
Buy vs. build for IT leaders
From Zapier to self-hosted n8n: when the switch pays off.
What should be up and running?
In 30 minutes on video we work out what should be built and give a first assessment of scope and timeframe. Or describe it to us in three sentences.
On working days we usually reply within 24 hours.