How we work: from first call to launch

We get the same question in almost every first call with a new client: "What actually happens now?" It's a fair question. Most people have been through a project that went sideways — vague deliverables, an agency that vanishes after launch, or a quote that doesn't match what actually gets built.

So here's the process, no detours.

01. Strategy

We never start with code. We start by understanding what you're actually trying to achieve — the business goal, not just the feature list. That usually means one or two conversations where we ask a lot of questions: Who is this system for? What makes it a case for bespoke, rather than picking an existing tool off the shelf? What happens if this isn't done in six months?

Out of that comes a clear architectural direction and a concrete scope — before a single line of code is written.

02. Design

Interface and system architecture take shape together, not one after the other. We prototype early, especially for the parts of the product where the user experience decides whether people actually use the system. You see and sign off on direction before we build further — no "big reveal" after three months of silence.

03. Development

This is where most agencies would show you impressive buzzwords. We keep it simple: typed contracts, code review on everything that ships to production, and continuous integration so every change is tested before it lands. You get regular demos, not a black box that opens at launch.

We work as one accountable team — the same people through the whole project. No handoff to a "maintenance team" you've never met.

04. Optimisation

Before launch, we go through performance, accessibility and technical SEO systematically, not as a last-minute checklist. A system that's slow or hard to find online doesn't solve the problem it was built to solve.

05. Scale

Launch isn't the end of the partnership — it's where the real work starts to show. We watch how the system behaves under real usage, fix what needs fixing, and stay involved when the next phase of the product needs building. Most of our clients — Frigg Kantine and Bildeler.no among them — we've worked with for years, not months.

What this means for you

No chain of vendors pointing fingers at each other. No surprises on the invoice because "that wasn't part of scope." And no situation where the person who understood your system best left the project three months ago.

Just one team, accountable for the whole journey — from the first conversation to long after the system is in production.