Who builds BrushQuote
BrushQuote is built by Mohd Haaziq, a solo founder and software engineer working on the app full-time since 2025. The product, the backend, the website you're reading, and the editorial guidelines for every blog post on this site come from one person — there is no content team and no ghostwriting agency.
That matters because most painting contractor advice on the internet is written by SEO agencies who have never quoted a paint job and have never sat with a homeowner arguing about a deposit. The articles on this blog are written from primary research: real US contractor licensing statutes (Cal. Bus. & Prof. Code, NJ HIPR, Florida Stat. §489), real federal regulations (FTC Cooling-Off Rule, EPA RRP), real manufacturer technical data sheets, and real conversations with painting crews using BrushQuote in production.
What BrushQuote does
BrushQuote turns a 10-minute jobsite walkthrough — photos, voice notes, room measurements — into a professional two-page PDF proposal with line-item pricing, scope of work, and a signed-ready contract. From the painter's iPhone, in 15 minutes start to send.
The app targets US residential painting contractors — solo painters and small crews of 1–10 people. We don't try to serve large commercial paint shops with their own estimating departments. The product is opinionated about residential workflow, residential pricing, and residential contract conventions.
Editorial standards for this blog
Every blog post on brushquote.app/blog/ follows a consistent set of editorial rules:
- US-residential context only. No UK, Australia, or commercial-only advice mixed in.
- Specific numbers, not adjectives. Dollar ranges, percentages, hour benchmarks, product brand-and-line names.
- Verifiable citations. Federal regulations cited by full code reference (40 CFR 745, 16 CFR 429). State statutes cited by full chapter and section. Industry standards cited by issuing body (PDCA, ASTM, AIA).
- Limitations called out. Each article ends with a Caveats block stating what the advice does not cover — state-specific exceptions, commercial overlay, evergreen vs time-bound numbers.
- One topic per post. No 12,000-word kitchen-sink guides. Each post answers one practical contractor question end-to-end.
The technical stack
Open about the stack because painting contractors deserve to know what they're trusting their business workflow to. If you're a fellow founder considering similar tooling, the AI proposal software guide walks through the trade-offs.
How to reach me
Email: [email protected] — for product questions, partnership requests, or feedback on a blog post.
Support: support.html for in-app issues, password resets, and subscription help.
Privacy / data deletion: [email protected].
If you're a painting contractor running a US residential crew and want to flag a number in a blog post that doesn't match your reality, please email — those corrections directly improve the next revision.