ReferencesXtraMile
They decided what every page should do. We built all of them.
XtraMile is a Norwegian AI-first learning platform, and its website is built to convert: pricing, plan comparisons, solution pages, customer stories. XtraMile briefed the structure and the goals for each page, and we built the module library and then assembled the pages on it ourselves, rather than handing the library over.
- 6
- years of continuous cooperation, since 2020
- 50+
- modules built, maintained and documented
- 3
- redesigns of the website since 2020
- 2
- languages the website is built to run in
A different kind of brief
Here we build the pages, not just the parts.
On our longer partnerships the deal is simple: we hand over a module library and the client’s marketing team runs it. XtraMile sits at the other end of that spectrum. They brief the pages (what each one is for, what it needs to say, where it sits in the funnel), and we build them.
So the module library and the pages made from it are the same job here. A pricing table, a plan comparison, a customer story: each one is a specific brief, built to it, and then made to hold up everywhere else it will be reused.
What a module ships with
Built once, reused across the funnel
The same card, table and call-to-action blocks carry the pricing page, the solution pages and the campaign landers.
Every breakpoint, not just the two drawn
A plan comparison that reads at desktop width has to still read at 375px, without becoming a scroll nobody finds.
Both languages in the same template
One module, two locales, and no forked copies to keep in sync as the site changes.
Behaviour under real content
Tested with three plans and five, with the image missing, with a heading twice the length of the one in the design.
A page a week is a normal week.
Because we build the pages as well as the parts, the turnaround matters more here than anywhere else. A new plan tier, a new comparison row, a campaign page for next month’s push: these arrive as a short brief and go live without a rebuild.
That only works if the library was built for it. Every module that goes in is one we expect to reuse on a page nobody has asked for yet, which is why the states get tested before they’re needed rather than after.
Different depth of involvement than our long-running partnerships, same underlying discipline: build it so the next change is cheap.
More references
Want the pages built, not just the components?
We can take the module library, the pages, or both. You decide what each page has to do. Tell us what exists today and we’ll tell you what it would take.