Skip to main content

How we work

We research around your team

In short: We fit around your company, not the other way round: the kind of project you need, where your team is with AI, and whether we work inside your systems or in ours and hand everything over.

9:41100%
User interview · PriyaGranola · 32 min · recording

Walk me through choosing a plan last time.

Honestly I gave up. I couldn't tell which one covered my whole team.

What would have helped?

Just show me the team option first.

Insight · 7 of 9 people

Teams can’t tell which plan covers them

Interviews

5 of 8 done

Highlight

“I couldn't tell which plan covered my team.”

Theme · plan confusion ×4

The process

A process that adjusts to the project

  1. We talk to your users and dig into your data to understand what's really happening.

  2. We design more than one direction from your real components and put working prototypes in front of users. One sign-off with you before engineering starts.

  3. The chosen direction becomes front-end code and components, in your repository or ours, with tracking built in. Your engineers review it. Your team decides when it goes to production.

  4. We test with real users and real traffic, and record what we learned so the next decision starts from evidence.

  5. Business and user needs are always evolving. We use what we learn to agree the next priority with you.

Built around you

We fit around your team's needs

  • The kind of projectA defined project, an ongoing partnership, time embedded with your team, or advisory and audits. Most start with a short discovery.
  • Where your team is with AINot started, experimenting or all in. We start from where you are.
  • Your systems or oursWe work inside your repository and tools, or in ours and hand everything over.

Ways to work

Flexible ways to work together

Start where it makes sense for you. Most people start with a short discovery, then choose how to carry on.

Start with a discovery period3-10 days depending on your needs
  1. 01

    Defined projects

    A clear scope, a start and a finish. For example, a research study, a redesign of your onboarding, or validating a feature before you build it.

  2. 02Preferred

    Ongoing partnership

    A set amount of senior time each month that moves with your roadmap. This is how we prefer to work. The longer we work together, the more we know, and the faster good decisions come.

  3. 03

    Embedded with your team

    Remote and part-time, but working inside your processes: your stand-ups, planning, tools and ways of working, alongside your engineers and product people for as long as you need.

  4. 04

    Advisory and audits

    Short, senior reviews when you need a clear outside view. A UX audit of a key flow, a review of what your analytics can tell you, a design system review, AI workflow setup or coaching.

Platforms

We work in the tools you already use

Whatever your stack, we work inside it: research, design, build and measurement. These are the tools we use most, and we're comfortable with their equivalents.

Research

Design

Build

Test and measure

Faster research, design and build, with a person reviewing every output and your team approving every release.

Your options

Alternatives to Antiphono

Hiring takes months and gets you one discipline. A fractional lead brings judgement, but only a day or two a week to act on it. AI tools in your engineers' hands make prototypes fast, but nobody decides what to build or checks it worked. We bring senior judgement and real output together.

More judgement ↑

More output →

A fractional lead

AI tools alone

Hiring

Antiphono

A fractional lead
Judgement, a day or two a week
AI tools alone
Fast prototypes, nobody deciding
Hiring
Months away, one discipline
Antiphono
Senior judgement and real output

Standards

Standards, data and your IP

  • AccessibilityWe design and build to WCAG 2.2 AA.
  • Personal informationHandled under the Australian Privacy Act, and the EU and UK GDPR where they apply.
  • Your IPEverything we make for you is yours.

How we work FAQs

Closely. We work in your repository or ours, and follow your conventions. Your engineers review and merge our pull requests like any other, and your team decides what goes to production.

Front-end build

Yes. It's built from your design system components and reviewed by a person before your engineers see it. It then goes through the same review as any code your team ships.

Front-end build

No more than a senior hire. We agree priorities with you, then get on with it, and you'll always know what we're working on and why.

Flexible ways to work together

Usually with a discovery: 3-10 days depending on your needs, quoted up front. We define the problem properly, build something you can click, and give you a plan for what comes next.

Book a call

Last updated

Book a call

Let’s talk about your product

Book a call. We’ll talk about where your product is, what’s getting in the way, and whether we’re the right fit.