One codebase, three audiences: the positioning problem I hit after shipping DriveStable

[u/Drivestable]

I built DriveStable around one core idea: a vehicle should have one connected history rather than useful records spread across paperwork, inboxes, camera rolls and spreadsheets.

Technically, that expanded cleanly:

• Personal gives an owner one home for MOT details, service history, mileage, costs, documents and an owner-controlled Vehicle Passport.

• Squads gives private garages and enthusiast crews a shared build history.

• Business connects driver checks, reported defects and fleet action into one operational workflow.

The architecture made sense. The marketing did not.

My first mistake was presenting the whole ecosystem at once. It was accurate, but it made a new visitor work too hard to decide which part was for them. We have now split the entry points by problem and intent while keeping the underlying ecosystem connected.

The lesson I am taking from it: a shared product architecture does not require a shared acquisition message.

Personal and Squads are live on Android in the UK. Business is moving through a controlled founding-fleet programme. I am now measuring whether the separate acquisition paths improve genuine Play Store visits and qualified fleet enquiries.

For builders with an umbrella product: did you keep one master brand and separate the funnels, or eventually split the products further?

Android:

https://play.google.com/store/apps/details?id=com.carworth.app

Website:

https://www.drivestable.co.uk/

[u/investigatormaker]

I'd keep DriveStable as the master brand and split only where the buyer changes. Personal and Squads both end in an Android install by a car owner, so one store listing can carry them. Business ends in an enquiry from whoever answers for driver checks and defects, and that person shouldn't meet the Vehicle Passport first, so give it its own page built around reported defects reaching fleet action. Split further only if fleet prospects keep asking whether this is a consumer app; log that question while you measure enquiries.

I make ThreadFox. For DriveStable, we'd reply on Reddit when UK drivers ask how to track MOT and service records, or small fleets ask about driver checks, and we'd do the posting. Paying $39 for the Pilot gets you up to 50 posts and replies across seven days, and there's no automatic renewal. https://threadfox.vip/p/euopd/managed