1.1 sLCP, 38 templates
Nordic retail platform
Relaunch on a shared design system across web and app. Median LCP fell to 1.1 s and conversion rose 24% in the first quarter after launch.
Oriel Digital. Websites, search and software from one engagement team.
Capability brief · Autumn 2026
Websites, search and software from one engagement team. Every sprint is tied to a revenue hypothesis you can audit.
Websites
Web and search, engineered from brief to revenue
One console for site performance, rankings and attributed revenue. The engagement team balances all three every sprint and explains every change it makes.
See how an engagement runs →
See how an engagement runs →
Websites
Performance-budgeted sites on a design system, instrumented for conversion from the first template.
- Design system and component library
- CMS with editorial workflows
- Performance budgets enforced in CI
- Conversion instrumentation per template
OutcomeEvery template ships under 1.2 s LCP and reports its own conversion.
Search
Technical SEO, content clusters and digital PR, reported as revenue rather than rankings.
- Technical SEO and crawl budget
- Content clusters built from demand data
- Digital PR and link acquisition
- Rank and revenue attribution
OutcomeOrganic revenue reported against a quarterly hypothesis.
Software
Native apps, web apps and internal tools, measured on retention after launch, not on launch day.
- Native iOS and Android
- Web applications
- Internal tools and admin
- Integrations and typed APIs
OutcomeRetention and crash-free rate on the board report, not launch day screenshots.
Nordic retail portfolio / This sprint
Autopilot onLCP 1.2 s · Pass
Good evening, Mara
The programme is on track. What should the team prioritise this sprint?
+0% organic sessions
0.0 s LCP at p75
€0 attributed revenue
＋ Site⚡ Playbooks⚙ Options
Data sourcespricing-page
Search Console
Queries and clicks · every hour
Real-user vitals
Field data · every pageview
You
Sites that measure themselves
Analytics, Search Console and real-user vitals stream into one view per page template.
Position drops below 5Trigger
Refresh content clusterAction
Hold canonical structureGuardrail
Search that compounds
Chain a trigger and a few actions into a playbook once. Pages are refreshed when rankings slip, before traffic does.
Release rationalev4.2Shipped ✓
Checkout drop-off peaks on step 3. Shipping the one-tap wallet lifts completion by 11% and is worth €1,140 a day, while the design system stays untouched for the redesign.
Ship every release with a reason
App builds go to the stores automatically, inside quality gates you set once and audit any time.
Performance budgets
Every template ships under 1.2 s LCP and 100 KB of JavaScript, enforced in CI.
Search telemetry at page resolution
Rankings, clicks and crawl data stream in, deduplicated and time-aligned by default.
Explainable recommendations
Every change ships with a plain-language rationale and a one-click rollback.
Software
Products built for retention, not launch day
Native iOS and Android, web apps and internal tools from one delivery team, with typed SDKs, staging replicas and replayable analytics.
Read the delivery method →
Read the delivery method →
Nordic retail appiOS and AndroidLive
Daily actives64.2k
Crash-free99.3%
Today€41.7k
Checkout flowHealthy21.4k
Search flowHealthy19.8k
Push campaign 14Paused0
Onboarding v7Healthy23.0k
Agent sessionone_tap_wallet.tsSandbox
Ask your agent to change the feature…
Agent-native delivery
Describe a feature in plain language. Our engineers and agents write, test and ship it against a staging replica of your product.
events.tsProduct eventsEvent received · 14 ms
// subscribe to product events oriel.events.on("funnel.drop", { screen: "checkout-3", threshold: 0.12, action: "alert.team" })
Real-time product events
React to funnel drops, crash spikes and rank changes within milliseconds.
Terminaloriel-cliRunning
$ oriel pages bulk --market nordics \ --tag "cluster:insurance" --strategy refresh ✓ 38 templates validated ✓ 214 pages staged
Publishing pages0%
Bulk operations from the CLI
Stage and publish hundreds of page changes at once, with dry-runs and automatic rollback.
sandbox-replicaReplay · Black Friday 2025Dev
retail-staging38 screens mirroredStaging
retail-prod412k users liveProd
Every environment in one place
Sandbox, staging and production, side by side.
Playbook runsLast 24h48 ok
content_refresh · 2m ago · ok
release_gate · 14m ago · ok
Playbook logs
Trace every run, input and outcome.
Status14 languages
Site healthyAll 38 templates reporting
ENDEFRJAES
Localized delivery
Ship in 14 languages, with local units and market rules.
Typed SDKs
TypeScript, Swift and Kotlin clients generated from one schema, versioned together.
Staging replicas
Replay any historic day against your release before it touches real users.
Webhook retries
Exponential backoff and dead-letter queues for every event subscription.
Platform adapters
Shopify, Stripe, HubSpot and Salesforce connectors with unified event formats.
Role-based guardrails
Cap scope per team, per site, per agent, enforced at the API.
Attribution ledger
Hourly-matched revenue exported straight to your board reports.
How an engagement runs
Four stages. Each one ends with a number the board can read, and each one can end the engagement.
- 1
Diagnose
2 weeksAnalytics, search, codebase and funnel audit.
Output: a ranked list of revenue hypotheses. - 2
Commit
1 weekOne hypothesis, one number, one sprint plan.
Output: a plan the board signs. - 3
Build
2-week sprintsShipped to production every sprint, with performance and quality gates in CI.
Output: a release every two weeks. - 4
Audit
End of every sprintThe number is measured against the hypothesis. Continue, pivot or stop.
Output: a decision, in writing.
We stop work that does not move the number.
Results
Organic revenue+38%In two quarters. Nordic retailer.
Median LCP1.1 sAcross 38 templates. Insurance comparison site.
Crash-free sessions99.3%After re-platforming. Logistics app.
Checkout completion+11%From one-tap wallet. Retail app.
Example engagements, figures illustrative.
Selected work
+38%organic revenue
Insurance comparison search programme
412 pages refreshed against a quarterly revenue hypothesis. Organic revenue rose 38% in two quarters, reported in the board pack each month.
99.3%crash-free sessions
Field logistics app
Native iOS and Android for drivers and dispatch. Crash-free sessions reached 99.3% and the store rating settled at 4.7.
Engagement models
Three ways to work with us. All three are scoped after the audit.
Audit
Duration2 weeks
TermsFixed fee
OutputRanked hypotheses and a 90-day plan
Sprint retainer
DurationOngoing 2-week sprints
TermsOne cross-discipline team
OutputMonthly audit against the number
Fixed-scope build
DurationDefined product
TermsMilestone billing
OutputShipped product with a 12-month warranty
Insights
Why most relaunches lose revenue for a quarter
Redirect maps, template parity and the audit that prevents the dip.
Attribution the board will actually read
One number per channel, one page, reconciled to finance.
The case against launch-day metrics
Retention at day 30 predicts the P&L. Downloads on day one do not.
Questions we are asked first
How long until we see results?
Search: one to two quarters. Websites: the first sprint. Software: the first release.
Do you work with our in-house team?
Yes. One combined team, one sprint review, and we own the number.
What do you need from us?
A decision maker in the sprint review, and access to analytics and code.
Where are you based?
Copenhagen, working across the Nordics and the UK. Remote-first.
What happens if the hypothesis is wrong?
We say so in the audit and re-plan. You never pay to continue work that does not move the number.
Start with the audit.
Two weeks, one ranked list of revenue hypotheses, and a 90-day plan you can take to the board.
Prefer email? Write to hello@oriel.digital