Web Case Study
Website and CMS Rebuild for a Web and Marketing Agency
Agency rebuild, built side by side
Scroll to move through the full page
DevOdin on desktop and mobile
Overview
A rebuild of devodin.com, a remote-first web design and digital marketing agency, delivered as a collaborative project between the DrieVerse and DevOdin teams. It moved from a static template to Next.js with Payload CMS.
DevOdin is a remote-first web design and digital marketing agency serving small and mid-sized businesses in the US, the UK and Europe. This was a collaborative project between the DrieVerse and DevOdin teams: DevOdin owned the brand, the voice and the client knowledge, and DrieVerse led the strategy research, the build and the search work.
The challenge
The agency's site was a static template that said more about the template than the agency. It listed nine services, carried placeholder content, and could not be updated without editing files.
An agency's own site is the first piece of work a prospect judges. DevOdin's was a purchased template carrying the template's own filler, a menu of nine services that no small team could deliver equally well, and no way to publish without touching code. It looked like every other agency site, which is the one thing an agency site cannot afford.
What we built
The DrieVerse and DevOdin teams rebuilt it together on Next.js with Payload CMS. The offer was cut to five researched service lines, and every page was built to rank and to be edited by the agency itself.
We started with the offer, not the design. Three separate research streams on competitors, search demand and delivery margin all pointed the same way, so nine services became five: websites and ecommerce, brand identity, search and content, CRM and AI automation, and marketing. The site was then rebuilt on Next.js with Payload CMS inside one application, with services, industries, posts and work items as content the agency edits itself. Sitemaps, llms.txt and structured data are generated from that content model rather than maintained by hand. Every route was audited across technical SEO, content, schema, GEO, performance and internal linking, round after round, until the scores held on the live site.
- Service strategy research that cut nine services to five
- Next.js front end with Payload CMS in a single application
- Service, industry, blog and work pages the agency edits itself
- Generated sitemap, llms.txt and structured data
- Nine rounds of SEO, GEO and performance audits
- Deploy pipeline that ships the app and nothing else
Results
The numbers below are what changed for DevOdin after DevOdin shipped.
Technology used
We are technology agnostic by policy. This is a record of what DevOdin required, not a house standard.
Services behind this project
DevOdin drew on 3 services from our catalogue, matched to what a web project like this actually needed.
Web development
Browser based products and sites built as systems, not as decorated pages. The structure, speed and maintainability survive past launch.
Explore web development →Custom software development
Bespoke systems for teams with a very specific requirement. An off the shelf product would force them to change how they work.
Explore custom software →IT consulting
Independent advice on architecture, tooling, and sequencing. For organisations deciding what to build, what to buy, and what to leave alone.
Explore IT consulting →This work sits inside our Run solution, for teams facing the same problem.
Related case studies
3 more case studies from work we have delivered, starting with other web projects.
The full portfolio holds every case study we publish, grouped by discipline.
DevOdin FAQs
Each team owns what it knows best. DevOdin owned the brand, the voice and what its clients actually ask for. DrieVerse led the research, the architecture, the build and the search work. Decisions were made together, from one shared plan.
Because a small team offering nine services reads as unfocused and delivers unevenly. Research into competitors, search demand and delivery margin agreed on five lines with real demand and room to stand out, so the site leads with those.
It keeps one codebase and one deployment. Pages read content directly rather than over an API, the agency edits services and posts in an admin it controls, and there is no second server to patch and monitor.
With our own audit across technical SEO, content, schema, GEO, performance, keywords and internal linking, repeated after each round of fixes. The composite rose from 61 in the first round to 95 on the live site.
Planning something like DevOdin?
Tell us what you are trying to build. We will tell you plainly what it would take, including the parts that would not be worth doing.
Last updated 7 November 2026
Contact Us
Lahore, Pakistan · London, U.K · Austin TX, U.S · Toronto, Canada