Design Develop Now designed and built MyExpertPros in four months, closing October 20, 2026. It is field-service software and a verified pro directory on one account: a public website, an office app, iOS and Android apps submitted the same day, and an internal console.
Homeowners find a pro, request a quote, book, approve, and pay. Owners, dispatchers, and technicians run the same job from the office or the truck. Payments, texting, reviews, listings, and permissions stay in one backend, so the website and the phones cannot drift apart. Six months of post-launch support cover store review and the first production season.
Home-service companies run the job on free field software. Homeowners find those companies on a verified directory. The same business, the same customer, and the same job move between the website, the office, and the phone.
Homeowners and listing owners
Public directory
Search by trade and place, profiles, quote requests, booking, reviews, and claim a listing.
Owners and dispatchers
Office web app
The day’s board, customers, estimates, invoices, team, messages, and settings.
Owners, dispatchers, and technicians
iOS and Android
The same business in the truck: today’s work, clock and arrival, photos, estimates, invoices, and customer texts.
Submitted to the App Store and Google Play on October 20, 2026. The office runs the same jobs. The brand and icons are the same files.
MyExpertPros staff
Operations console
Listings, billing, usage, and the queues a live marketplace actually needs.
Staff tools for the public directory, billing, and the queues behind a live marketplace.
One motion
The job is one motion, on every surface.
1Customer
2Job
3Estimate
4Approval
5Schedule
6Work
7Invoice
8Payment
9Review
A homeowner can enter that motion from a city page, a booking link, or a text. A technician can finish it from the phone. Nothing in the middle is retyped.
Commercial shape
The commercial shape is simple on purpose. The software is free. MyExpertPros earns a small platform fee when a customer pays an invoice. The directory is a separate product: a free verified listing, then paid plans for profile tools and labeled placement.
Trust signals are earned. Paying does not buy a better rank.
Why it was a hard build
The hard part was keeping one product whole.
Several businesses, several roles, and several outside companies had to live inside one product without splitting into separate systems.
Two businesses, one record
A contractor can use only the directory, only the software, or both. A listing, a paid membership, a software account, and a team invite are different things. They still have to recognize the same company. Free software does not include a directory plan. A quote sent to a software customer opens as a real estimate. A quote sent to a listing-only pro stays lightweight. Reviews from paid work can publish on the public profile.
Four kinds of user
The owner sees the business. The dispatcher runs the day. The technician sees their own jobs and can collect on a job. The homeowner never gets an account inside the company. They get a link: approve an estimate, sign, pay, track a request, leave a review. The phone and the website are not allowed to decide who can see money, customers, or another company’s data. That decision stays on the server.
Money has more than one path
Directory plans bill on their own. Invoice card and bank payments run through connected accounts, with the platform fee taken in that flow. Checks, cash, and Zelle are recorded without pretending a card was charged. Deposits, partial payments, refunds, receipts, and downloadable documents all have to agree. Public payment and signature pages are unauthenticated on purpose, and they expire, revoke, and audit.
The directory is a publishing system
City and trade pages, county hubs, and business profiles are built to be found. Pages with too few verified listings stay out of the index until they qualify. Featured placement is labeled, capped, and turned off when a listing stops qualifying. License status comes from public records, starting in South Florida, and a business claims that record before it can receive work. Unclaimed pages show only what the public record already says.
The phone is a work tool
The apps cover the office loop and the truck loop in one binary: run a business or join a team by invite, clock in, share location only while clocked in, notify arrival, take photos, build an estimate, send an invoice, and answer a customer. Background location, push, camera, and store privacy answers were part of the submission, not a follow-up.
Outside systems, one product
Identity, card processing, connected payouts, business texting, transactional email, file storage, maps, an AI estimate assistant, an AI receptionist and website chat, and error and product analytics each have their own rules. Texts have consent, quiet hours, and stop handling. Review requests are tied to real jobs. Public forms are challenged. Releases can turn quotes, booking, reviews, checkout, and messaging on independently, and can stop payments without taking the rest of the product down.
How four months held
Designed as one system, then cut so each slice could ship.
The early plan treated a native app and live crew location as later work. Both shipped inside the same window, on the same backend, and both were in the store builds on October 20. Livestreaming and full accounting sync stayed on the roadmap. That line is what made the date real.
The behavior was written down first
An approved product spec, office and phone prototypes, and a directory prototype were the contract. Shared rules for money, job status, phone numbers, plans, and what each role can open live in one place. The website and the apps read those rules. They do not each invent them.
One backend is the product
Directory, office, phone, and the operations console are clients. Tenancy, roles, invoices, messages, and listing eligibility are enforced once. A change to what happens when an estimate is approved does not get rebuilt four times.
Commodity work was bought
Sign-in, card processing, SMS, email, and file storage came from established providers. The four months went into the home-service loop: claiming a license, matching a quote to a pro, options on an estimate, a signature, a schedule, a tech on site, a payment, a review.
Geography and packaging stayed narrow
Launch data started with South Florida license records and a fixed set of trades, not a national catalog. Software has one price. Directory plans are few, public, and labeled. That removed a configuration product from the critical path.
Shipping was gated
Format, lint, types, unit and integration tests, accessibility checks, and a production build are one sequence. A release deploys only a commit that passed it, refuses a change that would drop existing data, then runs a synthetic check before product switches turn on. Payments can be disabled on their own. That is what let a large surface area move weekly without a freeze at the end.
Done had a definition
October 20 was the close of the build: production web, submitted iOS and Android binaries, and the operating console behind them. Apple and Google review, carrier and payments approvals, and the first real contractor weeks sit in the six months after. The support guide, store privacy packet, and release runbook were part of the delivery, so the product can be operated by people who did not write it.
Brand
One mark for the website, the office, and the phone.
The mark is a house split into four trades: plumbing, painting, repair, and air conditioning. Navy and blue carry the wordmark. A lockup adds the line “Local professional experts.” The Certified Partner badge is a trust mark with a rule attached: it is earned, and paying does not buy a better rank on the directory.
The same files run on the public site, the office, the phone, and the marketing films, so a homeowner, a technician, and a video still are looking at one company.
The same identity is filed with logo design, and it is the system behind the icons and the films.
Icons
Trade icons, drawn once and used everywhere.
The icon system starts from the logo: bold, rounded shapes, one saturated color per trade, drawn so the directory, the office, and the phone can share them. Category tiles are the trades a homeowner browses. Service glyphs are the jobs under those trades.
Motion ships with the system. A fan turns, a drop falls, a bolt flickers. On this page the tiles loop so the motion stays visible. In the product each one plays once and lands on the static pose, and schedules, estimates, and invoices stay still. Reduced motion keeps the static mark.
Marketing films are part of the same engagement. They use this brand, these icons, and the product surfaces above, so the ads and the app describe the same company.
More films from this engagement will be added here.
The close
On October 20, 2026, MyExpertPros had a public directory, an office product, native apps in review, and a staff console, all on one account and one backend. The following six months are post-launch support: store review, production monitoring, and the fixes that show up when contractors and homeowners actually use it.
