Skip to main content

This site is in public beta. Read what that means.

Working with Veraclins

A thoughtful approach to building your product.

Bring us the work you need help with. We can take responsibility for development, work alongside your team, or contribute research, design and product management from the start.

Start where you are

01
An idea to explore

We can help understand the problem, research the audience and shape a practical first version.

02
A product ready to build

Bring your specification, designs and priorities. We'll work through the technical approach and plan delivery with you.

03
An existing product to improve

We can investigate friction, extend features, connect systems and improve reliability or performance.

04
A team that needs support

We can contribute the skills and capacity you need, working with your existing people and processes.

Different perspectives, one connected effort

Research, product management, design and engineering inform one another throughout the work. Understanding a user's difficulty can change a priority. Exploring a design can reveal a technical constraint. Testing working software can uncover a better approach.

Our team's experience includes user research and product pilots, commerce and administrative workflows, and the interfaces and integrations behind them. We bring those perspectives together to consider both what a product should do and how it will work in everyday use.

We agree the involvement your project needs and keep the people doing the work connected to the decisions. You continue to lead your business direction.

From first conversation to ongoing improvement

Every project starts from a different place. We agree which stages are needed, who leads them and what each should produce.

  1. 01

    Understand the work

    We discuss what you want to achieve, who the product serves and the constraints around it. Existing research, designs and technical information help us build on what you already know.

    What this produces
    A shared understanding of the work, open questions and the next step.
  2. 02

    Plan the approach

    We work through scope, priorities, dependencies and the technical approach. Where research or design is needed, we agree how it fits into the project.

    What this produces
    An agreed plan with responsibilities, an estimate, milestones and acceptance criteria.
  3. 03

    Design and build

    We turn the agreed scope into working software. You see progress at agreed intervals and have opportunities to review journeys, discuss decisions and provide feedback.

    What this produces
    Designs where needed, working software and a clear record of important decisions.
  4. 04

    Check the experience

    We test important workflows, review how the application behaves and address issues before release. Performance, accessibility and security checks are selected for the product and its risks.

    What this produces
    Software reviewed against the agreed requirements, with remaining issues and limitations made clear.
  5. 05

    Launch and hand over

    We prepare the release and check the important journeys in the production environment. We agree the access, documentation and walkthroughs your team needs to operate the product.

    What this produces
    A release and handover suited to the engagement.
  6. 06

    Maintain and improve

    We can provide ongoing maintenance, resolve issues and help plan improvements as your needs evolve.

    What this produces
    Support with an agreed scope, price and response expectations.

Working together

Clear responsibilities

You lead your business direction. We take responsibility for the technical work and agree where you want help with research, design and product planning.

Visible progress

We agree a rhythm for updates and demonstrations so you can see the work, review decisions and understand what comes next.

Decisions close to the work

The people working on the product contribute to decisions and explain the implications of different approaches.

Care with commitments

We scope work carefully around the available time and budget. If new information changes the plan, we explain the impact and work through the options with you.

The care behind the software

01
Important journeys

We check how people complete the tasks the product exists to support, including what happens when something goes wrong.

02
Thoughtful implementation

Code review, testing and understandable structure help us build software that can be maintained and improved.

03
Connected systems

We consider how changes affect the wider application, its integrations and the people relying on them.

04
AI where it helps

When AI is part of a solution, we assess it against the task it needs to perform. Evaluation can include accuracy, grounding in relevant information and behaviour when the system is uncertain.

Ways to work with us

Research and planning

Help understanding a problem, exploring approaches or defining a product before development.

A defined project

An agreed scope with a delivery plan and budget.

Support for your team

Additional product, design or engineering involvement in an existing programme of work.

Ongoing maintenance and improvement

Continued support for the software and the changes you want to make.

We'll discuss the arrangement that suits your product, priorities and budget.

What we need from you

Access to the people and information that help us understand the product, timely feedback, and someone who can make or coordinate decisions. We agree the practical details before work begins.

Common questions.

Who leads the product decisions?

You lead your business direction. We take responsibility for the technical work and agree how much research, design, planning and product management you want us to take on.

Read the full answer: Who leads the product decisions?
What do you need from us during the project?

Access to relevant people and information, timely feedback and someone who can make or coordinate decisions.

Read the full answer: What do you need from us during the project?
What happens if requirements, timing or budget change?

We explain the effect on the work and discuss the options with you, adjusting scope, order of work or the delivery plan as needed.

Read the full answer: What happens if requirements, timing or budget change?
What happens after launch?

We agree the handover your team needs, and can provide maintenance and further development with an agreed scope and response expectations.

Read the full answer: What happens after launch?
See all questions

Have a product to build or improve?

Tell us where you are and what you need help with.

Keep up with Veraclins

Get news about our products, the work we're doing and what we're learning.

    Unsubscribe at any time. Read our Privacy Policy for more information.