Skip to main content
// What we do

From first pixel
to final deploy.

Three services. One studio. Every project taken from concept to launched product — designed, built, and shipped by the same people who scoped it.

01 —

Product Design

UX / UIPrototypingDesign SystemsUser ResearchInteraction Design

Interfaces that feel inevitable.

Good product design is almost invisible. The user completes the task. The interface removes itself from the experience. Nothing confuses, nothing obstructs, nothing makes the user aware they are using software.

That quality doesn't happen by default. It is the result of decisions made at every layer — the hierarchy, the spacing, the motion, the words on the buttons, the error messages, the empty states. The things users never consciously notice are precisely the things that determine how a product feels.

We design with that in mind at every stage.

// What's included

User research & discovery

We don't design assumptions. We start with the people using the product, what they know, what they need, and where existing solutions fail them.

Information architecture

The structure of a product determines how it is understood. We define the hierarchy before we design the surface.

Wireframes & user flows

Not deliverables for client review — thinking tools for us. The wireframe stage is where we validate structure before committing to visual decisions.

High-fidelity UI design

Pixel-precise interface design built to production spec. Every screen, every state, every edge case considered.

Design systems

A component library built once, built well. The foundation that makes future development faster and future design decisions easier.

Prototyping

Interactive prototypes for user testing and stakeholder alignment. The product working before a line of production code is written.

// Best fit

  • Founders building a first product who need design from the ground up.
  • Existing teams with engineering capacity but no dedicated design function.
  • Products that have shipped but never had a proper design system.
02 —

Development

React / Next.jsNode.jsMobileAPIsPerformanceAccessibility

Clean code. No shortcuts.

Code is read more than it is written. The developers who inherit a codebase — whether that's a future team member, a client's in-house engineer, or us six months later — deserve to find something coherent. Something that communicates its own logic. Something that doesn't require archaeology to extend.

We build with that inheritance in mind from the first file. Not because it slows us down — it doesn't, over any meaningful timescale — but because it is the right way to build.

Performance and accessibility are not features. They are baseline requirements. We do not ship products that are slow or inaccessible and call it a v1 problem.

// What's included

Front-end engineering

React and Next.js for web. Production-grade, component-driven, accessible by default.

Back-end & API development

Node.js APIs, database architecture, authentication, third-party integrations. Built to the same standard as the front-end.

Mobile development

React Native for cross-platform mobile. One codebase, both platforms, no compromise on the native feel.

Performance optimisation

Core Web Vitals, bundle analysis, image optimisation, caching strategy. Fast is not optional.

Accessibility

WCAG 2.1 AA as the baseline. Semantic HTML, keyboard navigation, screen reader testing. Built in, not bolted on.

Deployment & infrastructure

Self-hosted via Dokploy or cloud deployment. CI/CD pipeline, environment configuration, monitoring setup. The product running, not just built.

// Best fit

  • Design teams with finished specs who need a precise engineering partner.
  • Founders who have validated an idea and need it built to production standard.
  • Existing products that have accumulated technical debt and need a rebuild done properly.
03 —

Brand Identity

NamingVisual IdentityTypographyMotionBrand VoiceGuidelines

The name, the mark, the voice.

Most brand projects start in the wrong place. They begin with what it should look like before establishing what it should mean. The result is an identity that is visually coherent but conceptually hollow — something that looks like a brand without actually being one.

We start with the idea. The name, the positioning, the thing the brand believes that is genuinely different from what its competitors believe. The visual system follows from that. The mark, the typeface, the colour palette, the motion — each one an expression of the same underlying thought.

A brand built this way holds up across every surface because it is rooted in something real, not assembled from trends.

// What's included

Naming

Brand name development, URL availability, trademark viability check. The name is the first thing the brand communicates — it deserves proper work.

Logo & mark

Primary mark, secondary lockups, icon variants. Built as a system, not a single asset. Delivered in every format you will ever need.

Typography system

Display, heading, body, and mono typeface selection and pairing. Licensing guidance included. The typeface is the voice made visible.

Colour palette

Primary, secondary, and semantic colour architecture. Light and dark variants. Accessibility contrast ratios verified across all combinations.

Brand voice

The words, the tone, the things the brand says and the things it never says. A voice guide that anyone writing for the brand can use.

Brand guidelines

A complete reference document for every future decision — internal use, agency briefs, hiring, partnerships. The system documented so it outlasts any single contributor.

Motion language

Core animation principles — easing, timing, transitions — so the brand moves consistently across every digital surface.

// Best fit

  • New ventures that need an identity built from scratch before they build the product.
  • Existing companies whose brand has outgrown what was built at launch.
  • Founders who know their product is good but whose visual presentation isn't telling that story.
// How we engage

Fixed scope. Fixed price.
No surprises.

Every engagement starts with a brief. We scope it together, agree the deliverables, and set a price. That price does not change unless the scope changes — and if the scope changes, we have that conversation openly before the work continues.

We do not bill hourly. Hourly billing creates the wrong incentives for everyone involved. It rewards slowness, punishes efficiency, and makes the client feel like every question costs money. We work on fixed price because it aligns us with the outcome.

We are not the cheapest option. We have never tried to be. The clients we work with are not looking for cheap — they are looking for precise, on time, and worth every penny.

// 01
Brand Sprint

Two to three weeks. A focused engagement for founders who need a brand identity built quickly and built well. Name, mark, colours, type, voice guide. Everything to launch with.

Deliverable: Complete brand identity system.
// 02
Product Build

Six to twelve weeks. Design and development from brief to deployed product. Suitable for new products and significant version changes. One continuous engagement, one team throughout.

Deliverable: Launched product.
// 03
Design Partnership

Ongoing. A retained engagement for teams who want Serpens embedded in their product development cycle. Regular design and engineering capacity, without the overhead of hiring.

Deliverable: Continuous output.
// Out of scope

We're selective.
Here's why.

We turn down more work than we take on. Not because we are difficult — because we care about the output. Taking on a project we're not the right fit for produces mediocre work, and mediocre work is not something we put our name to.

For the sake of clarity:

We don't do print design.

We are a digital studio. Packaging, editorial, signage — these are disciplines that deserve specialists. We are not those specialists.

We don't do SEO campaigns or paid media.

We build the product. How you market it is a separate engagement for a separate partner.

We don't take on projects where the brief is unclear and the client is unwilling to clarify it.

A project with a vague brief produces a vague product. We will help you write a good brief. We will not proceed without one.

We don't do spec work.

We do not work for free on the promise of a paid project later. The brief process is our due diligence. If the fit is there, we scope it.

We don't take on more than two client projects simultaneously.

Attention is finite. When we commit to your project, we are actually committed to it.

We don't do maintenance retainers for projects we didn't build.

We are happy to take over a codebase or design system we didn't create. That is a project, scoped and priced accordingly — not a monthly retainer on an unknown system.

// The process

Every engagement follows the same five stages: discovery, strategy, design, build, launch. The stages are not bureaucratic checkpoints — they are the natural sequence of careful work. We do not skip stages. We do not run them in parallel to save time and cost quality.

The process is documented in detail on the main page.

See how we work
// Start a project

Know what you're
building?

Tell us. We'll tell you if we're the right fit.
If we're not, we'll say so.

Start the conversation →

We respond to every enquiry within 48 hours.