How we engage with you.

Five services, and three ways to go on after the first project. Most projects start with a Teardown.

Five services, side by side.

Sorted from the smallest project to the largest. Every service except the Teardown starts with discovery.

Teardown

Start here

Best for

A site that no longer matches the business, a product that has outgrown its first version, or a brand that drifted across site, product, and decks

You get

  • A recorded walkthrough of what we found
  • A ranked list of fixes, each with its effort and impact
  • A review call
  • A scoped next step, if you want one

Brand identity

Best for

Founders before a launch or a raise, or a company whose identity no longer fits

You get

  • Name exploration, if you need it
  • Logo, logomark, and wordmark
  • Color and type system
  • Brand guidelines your team will use
  • App icon and social assets
  • Files for print and screen

Websites

Best for

Companies whose site no longer matches the business, and products getting ready to launch

You get

  • Positioning and site map
  • A visual system made for you, not a template
  • Copy and a voice guide
  • Motion and interaction
  • An admin your team can edit without code
  • Accessibility checked against WCAG 2.2 AA

Product design

Best for

Product teams whose interface has outgrown its first version, and founders shipping a first release

You get

  • Research and user flows
  • Navigation and structure
  • Interface and interaction design
  • A design system with tokens and components
  • A working prototype in code
  • Build with reLabs, or handover to your engineers

Design systems

Best for

Teams whose screens have drifted apart, and products about to add a second app or brand

You get

  • An audit of where your interface drifts, with counts
  • Design tokens for color, type, spacing, and motion
  • Components built in code and documented in Storybook
  • Rules for when to use what
  • Packages your engineers install, not files they copy

After a scoping call, you get a clear scope and a schedule.

Ways to work together.

Most projects start with a Teardown. After your first project, there are three ways to go on.

  • Start here

    Teardown

    A senior designer ranks what to fix first in your brand, website, or product.

    Book a Teardown
  • Brand and website together

    Identity and site designed as one system.

    Included
    Identity and website, with an admin your team can edit without code.
    Not included
    Anything outside the agreed scope
    Start a project: Brand and website together
  • Design partner

    Ongoing design for teams that ship every week.

    Included
    Weekly reviews in the browser, and the files, code, and design history from every release.
    Not included
    Build with reLabs, scoped separately
    Book a call: Design partner
  • Build with reLabs

    reLabs, Reveriext's engineering team, builds what we design.

    Included
    The code, yours at handover.
    Not included
    Anything outside the agreed scope
    Book a call: Build with reLabs

How a project runs.

  1. First call

    Where your brand, site, or product is today, and what has to change by when.

  2. Teardown or brief

    Your choice

    A Teardown ranks what to fix. Or send a brief and we reply.

  3. Scope and schedule

    After a scoping call

    One agreed scope and a schedule.

  4. Discovery

    Before design

    Three directions as clickable pages. You choose one.

  5. Weekly reviews

    Every week

    You review the real work in your browser on a preview link.

  6. Handover

    At the end

    reLabs builds it, or we hand the files, code, tokens, and design history to your engineers.

The fine print.

Every project includes the files, the code, and the design history. You own them at handover.

Yes. You keep the ranked list.

You do. At handover, you own the brand files, the source design files, the design tokens, the code, and the design history, in formats any team can build from. Working with reLabs afterward is an option, never a requirement.

Yes. We can send ours or sign yours before the first call. Tick the box on the brief form and it comes first.

Yes. We design in code, so we can work in your repository, follow your conventions, and hand over components your engineers can extend. Or reLabs can build it for you.

You can go on your own with everything you need, or keep us as a design partner. Some teams come back for the next launch instead.

Not sure which one?

Book a call. We'll tell you which service fits, or whether you need us at all.