← All builds

Build 01 / 02

MyHandyAI

"Snap. Solve. Save." — an AI assistant that gives homeowners and renters the confidence to fix things themselves, with step-by-step guidance generated from a photo, a voice note, or a few typed words.

0→1 LLM + RAG Multimodal Co-founder & Product Manager Mar 2025 — Present

Role

Co-Founder & Product Manager (Part-time)

Team

International, cross-functional — Engineering, Data Science, UX/UI

Stack

GPT-5 family, Gemini, Qdrant vector DB, RAG pipeline

Recognition

1st Place, PMA AI Accelerator Program

MyHandyAI mobile app hero screens — project overview with estimated time, cost, skill level, tools and materials, and step-by-step guidance, alongside a home screen showing ongoing and completed repair projects

01

Overview

MyHandyAI is an AI-powered home repair assistant that helps homeowners and renters tackle repairs and DIY projects without calling in a professional.

Two men looking at the MyHandyAI app on a phone while working on a home repair, tool belt and drill in view
"Describe a problem by voice, text, or photo, and the app generates a personalised, step-by-step repair guide along with a tailored tools-and-materials list."

Under the hood it combines an LLM with image recognition and contextual reasoning to turn scattered, generic DIY knowledge into one coherent walkthrough — the goal was to lower the barrier for novices, raise task success rates, and save people money on call-outs.

02

Customer challenge

DIY is a genuinely large market with a genuinely common failure mode: people want to fix things themselves, but don't trust themselves to do it right.

$800Bspent globally on DIY home improvement
$14.4BUK home improvement market
$11.7BUK DIY e-commerce revenue, 2024
~£106average cost per DIY mistake, UK survey

A UK survey found close to 5 million people worry specifically about making DIY errors, and that the average person makes about four missteps a year — expensive enough, cumulatively, to either put people off DIY entirely or send them straight to a professional for jobs they could have done themselves with the right guidance.

"I get so anxious about home projects that I end up just not starting them — I don't trust myself to do it right the first time." — paraphrased from DIY community interviews
Diagram of four DIY pain points — advice overload, fear of making it worse, cost and convenience, and emergency stress

03

AI Hypothesis

We believe beginner DIYers do not lack online instructions; they need confidence that the instructions apply to their exact situation. If MyHandyAI uses multimodal AI to understand the user's repair context and provide personalised, step-by-step guidance, then beginner DIYers will trust the product more than generic search results — leading to higher task completion, satisfaction, retention, and paid conversion.

AI isn't used to generate more generic repair advice — the internet already has plenty of that. Its job is to organise, filter, and personalise: reading a photo, voice note, or a few typed words; asking the clarifying questions a knowledgeable friend would ask; adapting guidance to wall type, tool availability, object size and weight; explaining why a question or a tool matters; and offering a safer path forward when the user genuinely doesn't know the answer.

"The AI should not rush to answer. It should first understand the repair context, identify uncertainty, and guide the user safely."

That principle shaped the entire interaction model. Instead of instant, generic advice, MyHandyAI asks clarifying questions first — then delivers a tailored tool list and repair plan.

04

Personas

Three segments came out of research. Only one was right for an MVP.

Liam, the Anxious Fixer

Primary persona — first-time homeowner or long-term renter, millennial/Gen Z

Goals

Complete home repairs confidently without hiring a professional; spend less time researching before starting.

Pain points

Uncertainty about doing it right, no guidance tailored to his exact situation, research fatigue, anxiety about costly mistakes.

Pat, the Confident DIYer

Deprioritised for MVP — experienced DIYer

Goals

Find reliable tradespeople and source materials efficiently — not looking for step-by-step help.

Pain points

Not actively seeking DIY guidance, so harder and more expensive to acquire through the channels that work for Liam.

Colin, the Tradesman

Deprioritised for MVP, shapes long-term roadmap

Goals

Earn supplementary income, spend less time on vague job requests and inefficient directory platforms.

Pain points

Customers describe problems too vaguely; time wasted quoting jobs that turn out to be something else entirely.

Colin points at a real future feature — a paid "Virtual Tradesperson" mode inside MyHandyAI — but he and Pat were both explicitly cut from MVP scope so the team could go deep on Liam instead of wide across three very different jobs-to-be-done.

05

Customer journey

Mapping Liam's end-to-end experience surfaced where the emotional low points actually are — and they're earlier than you'd think.

MyHandyAI customer journey map for Liam — seven stages from problem trigger through research, starting a project in MyHandyAI, diagnosis, prep, guided repair, and completion, with touchpoints, thinking, feeling, and opportunities rows

The emotional arc runs from anxiety and frustration during research, to cautious optimism once a task actually begins, ending in either relief (task succeeds) or regret (a costly mistake or a call to a professional after all). The friction points cluster early: an unclear problem definition, and conflicting advice scattered across YouTube, Google, and DIY forums — both of which happen before a single tool is picked up.

06

Data-driven feature prioritisation

20+ deep-dive interviews got us the "why." 200+ survey responses — sourced from Reddit DIY communities and in-store B&Q shoppers in the UK — got us the "how many, and who."

of people surveyed said they'd prefer to complete more home tasks themselves, if they had better guidance. 69.2% of respondents were aged 18–40, versus 29.5% over 40 — validating Liam as the right primary persona to build for first.

Insight 1 — people want bespoke help, as long as they trust the AI

"Smart repair suggestions based on my home, tools, and skills" scored 7.6/10 on usefulness. Openness to AI overall scored a more polarised 6.8/10 — some respondents were enthusiastic, others openly skeptical. The trust builders that came up again and again: personalised answers, visible proof of accuracy, reviews or recommendations, and visuals.

"I'd trust the AI more if it could actually look at a photo of the problem and understand it."— survey respondent

That pushed three features straight into MVP scope: letting users skip or rephrase clarifying questions, showing a plain-language "why we're asking this" next to each question, and adding a post-project rating so trust could be measured, not assumed.

Insight 2 — visual guidance isn't optional

Asked how they'd prefer to describe a problem: 33.8% said photo upload, 31.2% wanted a combination of inputs, 20.8% preferred text, and only 14.3% chose voice. "Custom repair guides with images" scored 7.3/10 on usefulness — visual input and visual output both beat text and voice outright.

That set the MVP interaction model: photo upload as a first-class input, and step-by-step guidance built from photos, GIFs, and short video clips rather than paragraphs of instructions.

07

AI model selection

Four criteria drove model selection:

01

Multimodal performance

Strong enough vision + language understanding to read photos and video of a repair site, not just text.

02

Latency

Fast enough to keep step-by-step guidance feeling responsive rather than a wait-for-the-model experience.

03

Cost efficiency at scale

Sustainable unit economics once usage grows past early adopters — not just cheap to prototype.

04

Room to extend

Headroom to grow into AR-guided repairs and regional building-code compliance in later phases.

We prototyped on the GPT-5 family, tiered by task: nano models for lightweight, fast validation and clarifying-question generation; mini models for summarisation, data extraction, and tool/material recommendations; and the full model reserved for complex, multi-step repair planning — balancing response speed against reasoning depth rather than running everything through the heaviest model by default.

Inputs

Problem descriptions (text or speech-to-text), photos and video of the repair site, context metadata (room type, existing tools, skill level), and external reference content pulled in via retrieval.

Outputs

Concise problem summaries, recommended tools and materials, bespoke step-by-step guides, cost/time estimates, safety warnings, and links to the most relevant video or product resources.

08

Data strategy

Two data sources feed the system: external reference content (YouTube, Reddit, Google Custom Search, manufacturer manuals — scraped weekly) and internal user data (photos, voice notes, project descriptions — ingested event-by-event as projects are submitted).

01 · Scrape & parseAPIs pull raw content, cleaned and filtered before anything touches the model.
02 · EmbedProcessed content is vectorised and stored in Qdrant for fast semantic retrieval.
03 · TagMetadata added for tools, materials, project type, and safety/risk factors.
04 · RetrieveRAG combines the most relevant external and internal context before the LLM generates a response.
05 · VerifyA hallucination agent and quality-check routines catch duplication and infeasible suggestions before they reach a user.

09

AI model validation

Five layers stand between a model's raw output and what a user actually sees:

Hallucination agentChecks every recommendation for factual grounding and real-world feasibility.
Match validationConfirms recommended videos, tools, and materials are actually relevant to the specific problem.
Question validationEnsures clarifying questions are clear, relevant, and answerable by a non-expert.
User feedback loopPost-MVP: users flag unclear or wrong steps, which feeds back into prompt tuning and retraining.
Human-in-the-loopPost-MVP: AI output is spot-checked against real tradesperson instructions for an accuracy score.

10

Architecture & AI model

MyHandyAI was designed as a multimodal AI repair assistant, structured in four layers.

Input layerText, voice, or photo — the user describes the task however is easiest, including uploading an image of the object, wall, tool, or repair context.
Reasoning layerThe AI interprets the task, identifies what's missing, decides whether an answer is required or optional, and adapts its guidance to how much uncertainty remains.
Knowledge layerA RAG system retrieves relevant DIY guidance grounded in trusted sources and structured documentation, with safety, tool, and material recommendations checked against known repair logic.
Output layerA personalised tool and material list, step-by-step instructions, a risk level and explanation, an effort estimate, relevant images or clips, and follow-up support during the repair itself.
MyHandyAI system architecture diagram — UI & interaction, LLM layer, AI agent layer, memory & knowledge base, external APIs, and cloud infrastructure

System architecture

User interfaceMobile-first repair assistant where users can start or resume projects.
Conversation & intakeCaptures text, voice, and image inputs.
AI orchestrationManages clarifying questions, user context, response structure, and task progress.
RetrievalUses a vector database / RAG system to retrieve relevant repair knowledge.
Validation & guardrailChecks whether the response is safe, complete, and appropriate for the user's context.
Output generationProduces the tool list, repair steps, risk guidance, effort estimate, and supporting visuals.
Project memoryStores answered questions, unfinished projects, completed steps, and repair history so users can pause and resume.
"I want to hang a mirror on my wall."

From five clarifying questions — dimensions, approximate weight, wall type, hanging style, existing tools — the AI has enough context to recommend the right tools, the right wall anchor, a step-by-step plan, the safety risks, an estimated time, and what to do if the user doesn't know their wall type or the mirror's weight. It's why the MVP proof of concept centred on "hang a mirror" — it packs in every decision point that matters for trust: object size, weight, wall type, tool availability, anchor selection, safety risk, and confidence during execution.

11

Product roadmap

  1. Phase 1Months 1–3 · MVP

    Core AI DIY assistance

    Text/image/voice input, AI diagnosis, tailored recommendations, step-by-step guidance, feedback collection.

  2. Phase 2Post-MVP

    Richer & more accurate

    Enhanced image analysis, video content integration, expert validation layers.

  3. Phase 3Growth

    Human + AI, together

    Custom step-by-step video guides, expert tradesperson integration, the Virtual Tradesperson feature for Colin.

  4. Phase 4Scale

    Network value

    Community features, deeper personalisation, ecosystem partnerships.

12

User stories & acceptance criteria

The MVP flow, screen by screen:

  1. 01Home screen — ongoing and completed home repair projects, start new project

    Entry point — start or resume a project.

  2. 02Describing the project screen — chat interface asking the user to describe the repair and upload photos

    Capture the problem via text, photo, or voice, with follow-up clarifying questions.

  3. 03Project overview screen — estimated time, cost, skill level, tools needed, and step-by-step plan

    Estimated time, cost, and skill level, plus the generated tools list and step plan.

  4. 04Tools and materials screen — required and optional items with prices, ratings, and Amazon links

    Required vs. optional tools and materials, with prices, ratings, and buy links.

  5. 05Step-by-step guidance screen — video guide, numbered instructions, tools needed, and safety warning

    Visual-first instructions per step — video guide, numbered steps, and safety warnings.

  6. 06Project completed screen — congratulations message and rating and review prompt

    Completion, rating, and feedback — closing the loop back into the product.

13

Risks & remediations

RiskWhy it mattersProduct mitigation
Safety & liabilityConfident but incorrect repair advice could cause injury or property damage.Added risk classification, contextual warnings and hard stops for high-risk tasks, with escalation to a qualified professional when the system lacked sufficient context.
AI accuracy & reliabilityInconsistent online sources or incomplete user inputs could produce misleading guidance.Built a curated, expert-reviewed knowledge base with retrieval-based responses, source validation and a safe "I don't know" fallback.
User trustAI-generated instructions or visuals that do not match the user's situation could create false confidence.Prioritised real reference media, clearly labelled approximations and explained why each step was recommended.
Beginner usabilityUsers may not know technical details such as wall type, material or drill suitability.Designed guided clarification with plain-language explanations, photo input and "I don't know" as a supported response.
Adoption & retentionUsers may return to Google or YouTube unless the experience is clearly more relevant and easier to follow. DIY tasks may also span several sessions.Tested guidance against existing search journeys, then introduced personalised steps, saved progress and resumable projects.

14

MVP

Scoped to months 1–3: text/image/voice input, AI clarifying questions, dynamic tool & material recommendations, visual-first step-by-step guidance, post-project feedback, and safety warnings throughout.

Acceptance criteria

The app had to let someone complete two core tasks — hang a mirror and fix a running toilet — using text, image, or voice input, and return step-by-step guidance and tool suggestions for both.

Launch ran through a beta waitlist on Reddit, Pinterest, and Facebook DIY groups, micro-creator outreach, and a simultaneous Product Hunt + Reddit launch — which is what got us to 200+ organic waitlist signups in four weeks with zero paid acquisition.

15

Metrics

What I'd track post-launch

Activation% of users who start a new project, complete their first repair description, and answer at least one clarifying question.
Guidance quality% of users who rate the guidance as relevant, how often they ask follow-up questions because they're confused, and how many AI responses get flagged as unclear, unsafe, or irrelevant.
Task completion% of users who complete every repair step, how many pause and successfully resume, and the average number of completed steps per project.
ConfidencePre-task and post-task confidence scores, and the change between them — the metric that most directly tests the product's core thesis.
Retention% of users who start a second project, saved projects revisited, and repeat usage by repair category.
Monetisation% of users who click through on tool or material links, interest in premium guidance, and conversion from free guidance to a paid subscription.

16

Business model

Four monetisation paths, not one — repair guidance, commerce, expert escalation, and ongoing home maintenance all sit on the same core product.

Freemium Core loop
  • Free — basic repair guidance for simple tasks
  • Paid — unlimited projects, advanced visual guidance, saved history, tool checks, priority support
Affiliate commerce Transaction-based
  • Tool and material recommendations linked to Amazon and hardware retailers
  • Revenue on every completed purchase, not just every session
Expert connection Escalation
  • Handoff to a trusted handyman when a repair is too risky or complex
  • Keeps users inside the product even when AI guidance isn't the right call
Homeowner subscription Recurring
  • Ongoing home-maintenance support, seasonal checklists, repair history
  • Turns a one-off repair into a standing relationship

17

Lessons learned

1. AI products need trust, not just intelligence

For home repair, users aren't only judging whether an answer sounds correct — they're judging whether they can safely act on it. That made trust the central product principle: the AI had to explain why it was asking, show uncertainty when it existed, and offer a safer fallback.

2. Personalisation starts before the answer

The single biggest improvement came from delaying the final instruction until enough context had been gathered. Asking clarifying questions first made every answer feel more specific, relevant, and trustworthy — even before the user saw a single step.

3. "I don't know" is an important user state

Beginner DIYers often don't have the technical detail a good answer needs. Designing for uncertainty — instead of treating missing information as a dead end — became a core part of the experience.

4. Visual guidance must be accurate to be useful

Images and video are powerful for DIY, but an irrelevant visual damages trust faster than no visual at all. That's what pushed the decision to retrieve real examples first, and only show approximations with an explicit caveat.

5. MVP discipline matters

The product could sprawl in a dozen directions — tool commerce, a handyman marketplace, AR-guided repair, insurance partnerships. The strongest MVP stayed on one loop:

describe → clarify → prepare → guide → support → complete

Staying inside that loop kept the focus on the thing that actually mattered: helping one person finish one repair with confidence.

Revisiting MyHandyAI pushed me to think about AI as more than content generation — as contextual decision support. It isn't a chatbot that answers home-repair questions; it's a guided system built around user confidence, safety, and getting the job actually done. The biggest lesson carrying into the next build: a good AI product doesn't just answer the question in front of it. It helps someone make a better decision in a moment they weren't sure about.