This page goes with our answer to your RFP. We are a web company, so instead of a long document we built you a website: how we would take over www.tomra.com, what happens in the first 90 days, and how we work every day.
Jan recorded this for the TOMRA team. Jump to the part you care about.
These three priorities come from what you told us and from 30 years of building and running websites.
The site is reliable, fast, usable and findable by search engines and AI agents from day one. Errors are fixed quickly and, better, caught before users see them.
We move from fixing to adding value: a predictable rhythm with something delivered every other week, working through the backlog of post-launch wishes.
Your PIM is planned for the end of Q1 or start of Q2 2027, about six months away. We start preparing now, so it goes live on time and connects to the website cleanly.
Day 0 is the day the contract is signed, whenever that is. Click any bar or diamond for the detail. Pick a signature date to see real calendar dates and check the US go-live against Christmas.
Before we sign: if you want a second pair of eyes on anything, call us. It costs nothing.
We first wrote this method down for Kentico websites and have since used it on Sitecore, Adobe and Optimizely platforms. The steps stay the same: understand the platform, take over responsibility without a service outage, then move to the full service level. Each step normally takes about four weeks. For TOMRA they overlap, because your site is live and needs support from the first day.
The ten things that happen in a good handover. Tick what is already arranged; whatever is missing, we plan around it.
The formal part is the SLA: priority levels with contractually guaranteed response and resolution times, set out in our RFP answer. The informal part is how we work: you write, someone answers.
Your 50 editors are spread across the world. If they enjoy working with Optimizely, they go the extra mile for your visitors. That does not happen on its own with a new platform, so we make sure they are never left alone.
Teams channel, phone, Jira tickets, email: whatever channels we agree. A wrong button, a forgotten step from training or an accidental publish gets a fast answer.
From week 4, sessions built on your editors’ real questions from the hotline: what we fixed, and how one country solved what another is stuck on. Not another training course.
When time is short, editors can send us a Word document, an image to resize or a page to translate, and our content team publishes it, within the agreed support hours.
118,000 content blocks is hard to work with. We sort out what is used, unused, duplicated or truly shared, and clean it up with your editors.
All delivery work lives in Jira. The plan is not a schedule written once at the start; we review it continuously as priorities, dependencies and capacity change. You see the same plan we do.
| What you get | How often | What it tells you |
|---|---|---|
| Live delivery plan in Jira | Always current | What we deliver now, what comes next, why in that order, and what each item depends on. |
| Sprint report | Every two weeks | What was planned, what was completed, and what was added during the sprint. |
| Release plan and release report | Every release | What goes live, how it was tested and approved, and how it went. |
| Retrospective record | Every sprint | What we learned and the actions we agreed, each with one owner, tracked until done. |
| Root cause analysis | After every critical incident | What happened, why, and what we changed so it does not happen again. |
| Service report and status call | Monthly report, weekly call | Issues found and resolved, SLA performance, site speed, traffic and security. |
A German medical technology company whose Optimizely website, with a headless Next.js front end, was delivered by another partner. We took over service and support of the live platform in March 2026 without transition downtime and stabilized it from day one, together with Optimizely.
Today: monthly support and releases, new features in parallel, and a full architecture analysis with a phased improvement plan.
Why it matters for TOMRA: we came in on Optimizely when things were not working, and fixed them. The same situation, on the same platform, this year.
More than 4 million content pages, and a site that cannot go down during a sale. We provide 24/7 support with guaranteed response times, maintenance and long-term development, and we supported the Paul G. Allen Collection sale, the biggest auction in history.
Along the way: 40% more website visitors and twice the time on site.
Why it matters for TOMRA: if Christie's trusts us with its digital presence around the clock, your site is in safe hands.
A global manufacturing brand. We rebuilt its global website for 50+ markets and languages and rolled it out, then grew into content operations, a loyalty program and a mobile app.
Long-term partner for platform development, support and content services.
Why it matters for TOMRA: the closest match to your site. A global manufacturer, a complex multi-country site, many rollouts, and a partner that grows with you.
The people who take over your site are the people who support it afterwards.
If you need a second pair of eyes or want to test an idea in the next two weeks, call any of us.