Websites, search and software from one engagement team,with every sprint tied to a revenue hypothesis you can audit.
Case 07 · Nordic retailMost agencies sell a website, a search retainer and an app from three different desks. We run them as one programme, because the revenue they produce is one number.
Sites built under a performance budget, instrumented from the first template, so the design system and the conversion data ship together.
Every template ships under 1.2 s LCP and reports its own conversion rate.
Technical SEO, content clusters and digital PR, planned against one quarterly revenue hypothesis rather than a keyword list.
Organic revenue reported against a quarterly hypothesis, not a traffic graph.
Native apps, web applications and internal tools, built on architecture that can be audited and kept, not demonstrated once.
Retention and crash-free rate on the board report, not launch-day screenshots.
Four stages, in order. Each one ends with a decision the board can read, and the last one repeats every two weeks for as long as the work pays.
Analytics, search, codebase and funnel audit. We read what the data already says before anyone proposes a redesign.
Output: a ranked list of revenue hypotheses.
One hypothesis, one number, one sprint plan. The board signs the number before the team writes a line of code.
Output: a signed sprint plan with a target.
Shipped to production every sprint. Performance and quality gates run in CI, so nothing reaches users that would move the number the wrong way.
Output: production releases, every sprint.
The number is measured against the hypothesis. Continue, pivot or stop. The audit is written for the person who approved the budget.
Output: continue, pivot or stop.
We stop work that does not move the number.
Organic revenue in two quarters, after a content cluster refresh planned against one hypothesis.
Nordic retailer
Median largest contentful paint across 38 templates, held by a performance budget in CI.
Insurance comparison site
Crash-free sessions after re-platforming a field app on native iOS and Android.
Logistics app
Checkout completion from one change, a one-tap wallet, shipped and measured in a single sprint.
Retail checkout
Example engagements. Figures are illustrative of the reporting format, not a client reference list.
Three engagements, each reported on the number the client signed for. The charts are the sprint audits, in order.
Relaunch on a shared design system across 38 templates, with the checkout rebuilt as a native component in the same sprint cadence.
1.1 s median LCP. Conversion up 24% against the pre-launch baseline.
Read the case412 pages refreshed in priority order, each cluster tied to a revenue hypothesis and audited at the end of the sprint that shipped it.
Organic revenue up 38% over two quarters.
Read the caseNative iOS and Android replacing a hybrid app, shipped in seven releases with the crash-free rate as the only number on the board report.
99.3% crash-free sessions. 4.7 store rating.
Read the caseEvery engagement starts with the audit. What follows depends on what the audit finds and how much of it you want us to own.
| AuditTwo weeks, fixed fee | Sprint retainerOngoing two-week sprints | Fixed-scope buildA defined product | |
|---|---|---|---|
| Duration | 2 weeks | Rolling, reviewed every quarter | Set by scope, typically 3 to 6 months |
| Team | Strategist, engineer, analyst | One cross-discipline team, same people every sprint | Product team sized to the scope |
| Billing | Fixed fee | Monthly, with a monthly audit | Milestone billing |
| Output | Ranked hypotheses and a 90-day plan | Production releases every sprint, one number reported | The product, documented, with a 12-month warranty |
| Pricing | Quoted before we start | Scoped after the audit | Scoped after the audit |
The redesign is rarely the problem. The missing baseline is. What to measure before the old site is switched off.
One number, one page, one owner. A reporting format that survives the finance meeting.
Downloads and launch traffic measure the marketing budget. Retention and crash-free rate measure the product.
Search programmes show in one to two quarters. Websites report from the first sprint, because the instrumentation ships with the first template. Software reports from the first release.
Yes. We form one combined team with your people in the sprint, and we own the number regardless of who wrote the code.
A decision maker in the sprint review, and access to analytics and code. Everything else we can set up.
Copenhagen, working across the Nordics and the UK. The team is remote-first and meets clients in person at the audit and at quarterly reviews.
We say so in the audit and re-plan. You never pay to continue work that does not move the number.
Two weeks, a fixed fee, and a ranked list of what would move your revenue. Tell us what you are building and we will come back within two working days.
hello@oriel.digitalThe first conversation is a 30-minute call to decide whether the audit is the right start.