From a focused product bet to acquisition and enterprise growth.
A focused career tool that grew into an enterprise flagship product at WriteSea.
Read case study13,000+registered accounts in 90 days
For founders & venture teams
New bets.Better systems.
I research, design, build and test new products, features and internal tools—while your team stays focused on its roadmap.
See the workOne focused scope. £7,500 over four weeks. See what’s included
The person behind the lab
Led by Chris Adolphus
I founded CoverAI, which was acquired by WriteSea, where I went on to lead product. At Clan Labs, you work directly with me across research, design and development.
On working together
SquadPal
“He led research sessions that identified user pain-points and made product improvements leading to a 40% increase in retention.”
Robinson NouveauFounder · BondioEx CEO of SquadPalYara
“Chris applied a logical, methodical, and well-structured approach throughout and he helped us achieve the results the project needed by delivering our prototype.”
Martin GambleSenior Service Designer · YaraWritesea
“Chris led our pivot to enterprise and shaped the product around what those customers needed. His product work helped us retain 99.5% of our enterprise partners and cross $1.1M ARR.”
Leander HowardPrincipal GTM · GitwitThen Co-founder · WriteseaFICO
“We went from screens that were functional, to screens that were easy to navigate, nice to look at and fit the solution we were developing.”
Tom DunneDirector, Solutions Consulting · FICOSelected work / 01—03
Inside the lab
Small bets. Real products.
A closer look at the work.
WWillow Spoon KitchenView basket
Orders openGood food.
Ready for Sunday.
Ready for Sunday.
Roasted vegetable bowls, made to order.
Collect on SundayBirmingham · 12:00–14:00
A pre-order product, built in one week.
A closed beta with four sellers, shaped around one seller’s pre-order needs.
Read case study7 daysto deliver a usable pilot
Turning routine bug reports into reviewable fixes.
From report to production, with less disruption to planned work. Engineers retain review and approval.
Read case study8× fasterbugs and hotfixes resolved and shipped · team-reported
Offers & pricing
Two offers.
£7,500 each. Four weeks.
A first working pilot of the core workflow in week one. Weeks two and three are for testing, design and refinement; week four is for verification, documentation and handover. We agree the scope, acceptance criteria and required access before starting.
Product & feature bets
One product use case or feature
Test one customer need with a working pilot and evidence for your next decision.
- Evidence from user research
- A first working pilot in week one, refined with users in weeks two and three
- A recommendation: continue, change or stop
£7,500 / four weeks
Discuss a product or featureInternal tools
One internal workflow
Replace a manual workflow or costly software subscription with a tool built around your team.
- A review of your workflow and annual software costs
- A first working pilot in week one, refined with your team against agreed acceptance criteria
- Documentation and a practical handover
£7,500 / four weeks
Discuss an internal toolYour part
A decision-maker, access to relevant users and systems, and time for weekly reviews. We agree participant recruitment and access before starting.
At handover
You receive the working release, source code, design files, research findings and documentation, with a walkthrough. Hosting is set up in your accounts, with external running costs paid by you. Ownership and third-party licences are agreed before starting.
30 days of bug fixes included
For 30 days after handover, I fix bugs where the delivered work does not meet the agreed scope and acceptance criteria. New features and changes to the scope are separate. Optional paid maintenance can be agreed for ongoing support.
Delivery details & costs
Agree the boundaries
Before starting, we define who will use the release, the steps it covers, required integrations, recruitment, any data migration and what counts as accepted. If findings or access change, we agree the impact on scope and timing together.
Define a useful release
Week one delivers a first working pilot of the core workflow. Weeks two and three develop the agreed scope through design, testing and feedback. Week four checks the acceptance criteria and completes documentation and handover. For internal tools, we also agree permissions, failure handling and a rollout plan. A pilot provides evidence for a decision; it does not guarantee commercial validation.
Account for running costs
£7,500 before VAT, where applicable. Hosting, participant incentives and other external costs are agreed separately. For software replacements, we compare licence costs with building and running the replacement. The included bug-fix period lasts 30 days after handover. Further development and ongoing support are scoped separately.
Questions about scope, delivery or working together? Read the FAQ
From question to recommendation
A first pilot in week one.
Then tested and refined.
Scope and access are agreed before the engagement begins. The first pilot gives us something to test and improve with users. Documentation develops alongside the product and is completed at handover.
- Week 01
Understand & build
Understand the problem, design the core workflow and deliver a first working pilot.
- Weeks 02–03
Test, design & refine
Put the pilot in users’ hands. Use feedback to improve the design, develop the agreed scope and test what changes.
- Week 04
Verify & hand over
Check the agreed acceptance criteria, complete the documentation and walk your team through the product and next steps.
See if your project fits
30 min with ChrisTalk through the problem, the people it affects and what a useful first release could look like. We’ll discuss whether it fits a four-week engagement and what access or integrations it needs.
Bring the problem
A short description of what you want to test or improve, your current tools and any deadline. An idea or an existing workflow is enough to start the conversation.
Before work starts
We agree the scope, acceptance criteria, costs and start date, and confirm the access needed for a first working pilot in week one. Booking a call does not commit you to an engagement.
Choose a time using the Cal.com link below.
Frequently asked questions
Before you book.
What can you build in four weeks?
One focused product use case, feature or internal workflow. For example, a customer pre-order journey or a team request-and-approval workflow. We agree the scope and acceptance criteria before starting, including users, steps, integrations and access. A wider product or system replacement needs a separate scope.
If there’s a pilot in week one, what are the other three weeks for?
The first pilot covers the core workflow and gives people something to use and respond to. In weeks two and three, we use their feedback to improve the design, develop the agreed scope and test what changes. In week four, we check the agreed acceptance criteria, complete the documentation and walk your team through the product and next steps. Documentation develops throughout the engagement. Scope and required access are agreed before week one begins.
Can you work within our existing product?
Yes, following a review of your codebase, integrations and release process. We agree what can be delivered within four weeks, the access needed and how it will be released.
What does £7,500 cover?
Four weeks of discovery, research, design, development, testing and handover, plus 30 days of bug fixes after handover for the agreed scope. VAT applies where required. Hosting, participant incentives and other external costs are additional and agreed before starting. New features and scope changes are separate.
Who does the work, and what do you need from us?
You work directly with me, Chris. I own delivery without needing your team to build. I need one decision-maker for context, access and weekly reviews, plus access to relevant users for testing. We agree the start date once the scope and required access are confirmed.
What do we receive at handover?
The working release, source code, design files, research findings and documentation, with a walkthrough and a recommendation on what to do next. Hosting is set up in your accounts and you pay the external running costs. Ownership and third-party licences are agreed before starting, so your team can take the work forward.
Who fixes bugs or maintains the product afterwards?
For 30 days after handover, I fix bugs where the delivered work does not meet the agreed scope and acceptance criteria. This covers corrections to the delivered work, rather than new features or changes to the scope. Beyond that period, your team can maintain the product or we can agree optional paid maintenance. Further development and ongoing support are scoped separately.