Book a strategy call
Back to case studies
Legal Services, AI

Settle: Creating AI Co-pilot for UK immigration

How a legal tech product helping navigate immigration hired a CTO, a Product Designer and a Mobile Engineer.

Challenge

Settle is an AI co-pilot for UK immigration: a personalised roadmap that tracks someone’s status, counts their days of absence, holds their documents and tells them in plain English what to do next, across a web app and on iOS and Android. The users are people whose right to remain in the country depends on dates and paperwork, so a miscounted day or a missed deadline is not a usability complaint. The product also has to be genuinely useful while stopping short of legal advice, which Settle states openly that it does not give. That boundary cannot be handled with a disclaimer at the bottom of a screen. It has to be designed into what the product says, how confidently it says it, and where it hands the user to a regulated adviser instead.

Three requests went in simultaneously, across three functions rather than three seats on one team, into a company that had no engineers at all. The CTO role needed ten years and more of distributed systems design, with experience taking products from proof of concept through to production hardening in regulated environments, and a record of leading engineering teams rather than only building: TypeScript, Java and Python on Kubernetes and AWS. The Product Designer role needed six years and more on complex multi-stakeholder systems, design systems built and implemented rather than presented, and the full span from user research to interaction detail, on Figma. The Mobile Engineer role needed six years of cross-platform Flutter, because the product ships on iOS and Android alongside the web app, with Firebase, real-time handling over WebSocket and GraphQL, and local persistence through Hive and SQLite.

Each was screened against role aspects that required practical experience gained before the project. For the CTO that was regulated-domain delivery, because a product handling immigration records is judged on how it treats data before anyone looks at the roadmap. For the designer it was evidence of design systems running in production rather than in a portfolio. For the mobile engineer it was full-cycle ownership of shipped applications rather than feature work inside someone else’s. The CTO was matched first, 16 hours after the request opened, and then interviewed the designer and the mobile engineer alongside the founding team, so the two people who would build under that architecture were chosen with the person who set it.

3
Talents Secured
6+
Months Duration
16h
Time-to-hire

Outcome

Most companies hire these three functions a year apart and spend that year with one of them missing. Settle had none of them. All three requests were opened at once, on the reasoning that architecture, interface and build are the same set of decisions at this stage, and the CTO was in post quickly enough to help choose the two people who would work under those decisions.

  • Three requests across different functions, with the first engagement confirmed in 16 hours.
  • Technical leadership, product design and mobile engineering, covering the path from architecture through to what a user actually sees on three platforms.
  • A founding product team built from nothing with no recruitment overheads - Settle had no engineers before the CTO arrived.
  • Six months in the team of three delivers updates and new features to the application across architecture, design and the mobile build.
Communication was quick and clear, everything was delivered exactly as promised, and the quality exceeded my expectations.
Halyna Semchak
Halyna Semchak
CEO and Co-Founder, Settle

A Strategic, Multi-Phase Hiring Approach

Phase: Request

When the need for technical hires arose, all three requests opened together across three functions rather than separately. A CTO on distributed systems and regulated delivery, a product designer on design systems and research, and a mobile engineer on Flutter for a client-facing app on iOS and Android.

Phase: Matching

The team screened 9 candidates based on what each role would do from day one: production architecture for the CTO, shipped interfaces for the designer, and live apps on both stores for the mobile engineer, with only 4 shortlisted candidates moving to interviews.

Phase: Interviews

The founders interviewed the CTO and confirmed the engagement within 16 hours of the request opening, then interviewed the designer and mobile engineer with the new CTO present.

Phase: Engagement

All three engagements started with a part-time monthly workload, a set hour cap, built-in daily hour tracking and monthly reports with a detailed breakdown of hours.

Phase: Support

Six months of engagement, a team of three, and both workload changes and extra hours adjusted and approved as the build and app releases demanded.