RepairRoute

Repairs Routed by Urgency, From Report to Fixed.

Problem: Most landlords don't live next door to their tenants. When a pipe bursts at 2 a.m. and a kitchen floods, the tenant has to reach someone who may be hours or countries away, and hope the message gets read. A flood and a loose cabinet hinge land in the same pile of texts and calls. Nobody knows what to handle first, vendors are found in a scramble, and tenants are left wondering whether anyone is coming.

The solution: RepairRoute connects tenants, landlords, and vendors in one flow. A tenant reports a problem with a photo and a short description. The app checks the urgency immediately, tells the landlord why, and routes the job to the right kind of vendor. The tenant can follow each step until the repair is confirmed fixed.

How it works💯 Tenants: No signup or login. The device is recognized automatically. Report a problem with a photo, a one-line description, and a location in the unit. Each report gets a request ID, an urgency label, and a four-step tracker: Received, Triaged, Scheduled, Resolved. The tenant confirms when the repair is fixed, so the person living with the problem has the final say.

Landlords: A triage inbox sorts emergencies first, with a red banner and a count of emergencies needing attention. Every card shows the photo, the urgency, the reason ("Active flooding on property premises"), the location, and the time. Routine jobs get a suggested vendor, an estimate range based on the vendor's rate, and a one-line reason. The landlord can hire the suggested vendor, choose another, message the tenant, or change the urgency. Emergencies skip vendor matching and show a "Call emergency contact" action.

Vendors: Vendors apply through a "Become a vendor" form with their trade, rate, callout fee, and service area. Only approved vendors appear in routing. The creator reviews applications from a private admin page. Approved vendors receive job offers and can accept or decline with a proposed time.

Payments (demo): will be fully integrated soon.

Notifications: Each role has its own bell and unread count, and sees only its own alerts.

My process🧠 : I built RepairRoute in steps, testing after each one: Idea selection. I started with several ideas, including voice-first apps, document tools, and caregiver handoffs, and chose tenant repair triage because it has a clear user, a clear before-and-after, and several automated decisions. Core build. I wrote the first Base44 prompt for the tenant report form and the landlord inbox with urgency classification. Vendor routing and tracking. I added the vendor list, estimates, approval, and the four-step tracker for both sides. Testing like a user. I submitted real test reports and found problems: landlord replies didn't reach tenants, tenants had no way to find their requests, and some buttons didn't respond.

Full audit. I asked Base44 to audit the whole app without changing anything. It found that triage ran too late, demo data wasn't linked to devices, white text on the gradient was low in contrast, and the logo was unclear at small sizes. I fixed each issue with its own prompt and retested.

Design and branding. I moved from a plain default look to a blue gradient, pill buttons, rounded cards, clear urgency colors, a route-line logo, and restrained motion that respects reduced-motion settings. Vendor approval and payments. I added the vendor application and approval flow, then the tenant-confirmed completion and deposit flow.

Design decisions✍️: Red only for emergencies, so urgency is visible at a glance. A visible reason for every classification, so landlords can trust the triage and override it. One route line as the brand idea: from tenant, through the landlord, to the vendor, ending in a check mark for "fixed." Mobile first, because tenants report problems from their phones, usually at the worst moment. Tenant confirmation before final payment, so a landlord isn't asked to pay for unfinished work.

What I'd build next Real payment holding through a payment provider Background push, email, and SMS notifications Vendor ratings and a verified-documents check Multi-property and multi-landlord accounts Tenant history by unit, so landlords can see recurring problems Limits I'm upfront about Payments are a demo. Tenant recognition is per browser. Clearing browser data means a tenant has to look up a request by its ID. The admin page uses a passcode, which suits a demo but not a live product. Notifications currently work in-app.

Built with Base44 for the app, backend, and data. Work through on google drive. Every prompt, test, and fix was done by me, step by step.

QuoteFlow: a quote in 60 seconds, not 3 days.

Try it in 2 minutes: submit a quote on the home page (any email) and watch the AI estimate appear. Then open https://quoteflow-13124bc3.base44.app/demo to explore the owner dashboard, automations and lead timelines on sample data, no login needed.

Service businesses (mobile detailers, cleaners, landscapers) lose jobs in the gap between "can I get a quote?" and an actual number. Phone tag, forgotten follow-ups, customers who go cold. I built QuoteFlow on Base44 to close that gap automatically.

How it works:

• A customer fills one form on the public site. A backend function sends the request to Base44's InvokeLLM together with the owner's real rate card and pricing rules, and gets back an itemized estimate (SUV surcharge, pet hair add-on, travel fee, assumptions) in about 3 seconds. The AI never prices outside the rate card, and if the LLM is unavailable it falls back to the plain rate-card price and flags it.

• The customer gets a branded email with a private link and books in one click. The owner gets an alert with a private AI note (risks, upsells, questions to ask).

• A scheduled Workflow runs daily: quotes that have gone quiet for 48h get a friendly follow-up (max 2), then go stale after 7 days so the owner can call the live ones instead.

• A second Workflow emails the owner a Monday digest: leads, quotes, bookings, revenue, conversion and the most requested services.

• The owner dashboard is mobile-first: KPI tiles, a pipeline (kanban on desktop, filterable list on phones), and a full timeline per lead showing every email, automation run and status change. Settings control the rate card, pricing rules and follow-up timing.

How I built it: 3 Base44 entities with row-level security (customers never touch the Lead table, only token-scoped backend functions), 5 TypeScript backend functions, 2 scheduled Workflows created through the Base44 API, and a React + Tailwind frontend deployed with the Base44 CLI. I used Claude Code as the coding agent against Base44's official agent skills; Base44 provides hosting, auth, the LLM, email and scheduling. Verified live: real submissions priced by InvokeLLM, emails delivered, workflow runs completing on schedule for four days.

Live: https://quoteflow-13124bc3.base44.app · Owner dashboard sandbox: https://quoteflow-13124bc3.base44.app/demo