Skip to content
Codivine

Portfolio

Work we’re proud of.

The best way to understand what we can do is to see what we’ve built.

Websites and stores delivered
200+Websites and stores delivered
Platforms shipped to: web, iOS, Android
3Platforms shipped to: web, iOS, Android
Products built end to end
6+Products built end to end

Real estate technology

The area we've gone deepest in — several products for property businesses, across every platform an agency actually uses.

  • Web
  • iOS
  • Android

  • A CRM for property businesses

    Built around properties, buyer requirements and viewings rather than a generic sales pipeline.

  • A property platform across web, iOS and Android

    Including a separate client-facing site, so agents and their customers each get an interface built for them.

  • A second product for estate agents

    Focused on the day-to-day work of running viewings and capturing the leads that come out of them.

Mobile applications

Published apps on both stores, across consumer categories with very different demands.

  • iOS
  • Android
  • Web

  • Two published mobile games

    Real-time gameplay and the performance constraints that come with it — a long way from a form over a database.

  • A skincare app on web, iOS and Android

    One product delivered across three platforms with a shared backend.

  • Widgets for a nutrition tracking app

    Home-screen widgets for an established app with a large existing user base.

Websites and online stores

The volume work — and the reason the technical SEO opinions elsewhere on this site come from practice rather than reading.

  • Web
  • E-commerce

  • Over 200 websites and online stores

    Built, rebuilt or repaired, for businesses ranging from single-location operations to established brands.

  • Brand sites for international companies

    Including a global motorcycle manufacturer and consumer brands with existing design systems to work within.

  • SEO audits, fixes and implementation

    Across a large number of those sites — the diagnosis and the code changes, not one or the other.

Why there are no client names here

All of the above is work we delivered. What we don’t have yet is written permission from each client to publish their name, so we describe the work by sector instead of claiming logos we haven’t been cleared to use.

On a call we can be considerably more specific, including about the parts that were difficult — which is usually the more useful conversation anyway.

[ADD CLIENT PERMISSIONS][ADD NAMED CASE STUDIES]
Ask to see relevant work

What a published case study will contain

  1. 01ChallengeWhat was actually going wrong, in the client's words.
  2. 02Business contextHow the company operates and why that shaped the solution.
  3. 03GoalWhat we agreed success would look like before starting.
  4. 04SolutionWhat we built, and the decisions behind it.
  5. 05TechnologyThe stack, and why it was the right fit here.
  6. 06ImplementationHow it was delivered, including what changed mid-project.
  7. 07ResultsMeasured outcomes — only numbers we can stand behind.
  8. 08LessonsWhat we'd do differently. Every project has something.

Looking for something specific?

Each service page explains how we approach that kind of project, what’s included, and the questions worth asking before you start.

Similar project in mind?

Tell us what you're trying to build and we'll tell you honestly whether it's something we should be doing — and what it would take.

Let's talk

No specification needed. A description of the problem is enough to start.