The radical transparency cluster: /reviews, /roadmap, /commitments

Three pages, three commits, roughly six weeks of decisions about what to publish and what to hold. The transparency cluster is not a marketing exercise. It is the written record that AskBaily can be held accountable to.

What each page does

/reviews, from Wave 175, is the public review page. It lists every homeowner who has completed a closed-won project with AskBaily, with their permission, and their verbatim review text. Real names (first name plus last initial, with permission), real ZIP codes (partial, at the five-digit level), real project scopes, real outcomes. The page does not aggregate the reviews into a 4.7-star rubric. It does not hide low-rated reviews. The aggregate-rating schema we attempted in Wave 15.23 was removed in Wave 15.24 for policy reasons: Google's rich-result policy requires aggregated ratings to reflect ratings of the specific itemReviewed entity, and AskBaily's BBB rating is inherited from the NPLD parent organization, which is a different entity. We chose to publish the reviews without the synthetic aggregate.

Wave 175.1 corrected a date claim on the page (launch date mid-April 2026, not March). The correction happened in the same day the error was noticed. The git commit is 55285930, and the change is part of the public record at /roadmap.

/roadmap, from Wave 176, is the rolling wave log. Every shipped wave has an entry with date, title, and a one-sentence description. Every staged wave has an entry with the expected ship date or a deferred-reason. The page currently lists approximately 60 shipped waves covering the January-through-April 2026 arc, plus approximately 25 staged waves through the end of 2026. Nothing on /roadmap is speculative beyond 60 days; waves further out are documented but marked as directional, not committed.

The /roadmap structure is deliberately comprehensive. A homeowner looking for a specific feature can find whether it exists, whether it is in flight, and when it is expected. A contractor evaluating whether to join can see the velocity and the direction. A journalist writing about contractor marketplaces can cite a specific wave without asking us.

/commitments, from Wave 178, is the shortest page and the most consequential. It is the written contract between AskBaily and the homeowner: what we will always do, what we will never do, and what happens when we fall short. "We will always verify your contractor's license against the issuing board in real time." "We will never share your contact information with more than one contractor." "We will publish every wave we ship on /roadmap within 72 hours of shipping." Each commitment is dated, sourced to the wave that implemented it, and linked to the evidence trail.

Wave 179 added the /commitments page to the sitewide footer IA so the cluster is reachable from every page. Wave 177 did the same for /reviews and /roadmap. All three pages are one click from any page on the site.

Why the cluster exists

The thesis of AskBaily is that the contractor-marketplace category is structurally broken because every incumbent monetizes on information asymmetry. Angi monetizes on homeowners not knowing that contractors pay for leads. Thumbtack monetizes on homeowners not knowing that profile "verified" badges are self-attested. Houzz monetizes on homeowners not knowing which of their many favorites actually bids projects. HomeAdvisor monetizes on homeowners not knowing that a matched pro is one of seven matched pros.

If that thesis is right — and we think it is — then the correct strategic move for an entrant is to make information asymmetry impossible to maintain. The transparency cluster does that. /reviews publishes the roster. /roadmap publishes the operational pace. /commitments publishes the contract. If we ever violate a commitment, the homeowner does not need to reverse-engineer our policies from legal fine print; they can read the commitment, compare it to their experience, and escalate with a citation.

What Angi and Thumbtack cannot do

This one is the softest-seeming and the hardest to copy. Angi cannot publish a /reviews page that names every homeowner they closed a project with because their closed-rate on matched leads is structurally low — many leads result in zero contracts because the homeowner is bidding against seven pros. They cannot publish a /roadmap that lists every feature they shipped because the list would be dominated by lead-volume optimizations, not trust features. They cannot publish a /commitments page that says "we will never share your contact with more than one contractor" because their business model is sharing your contact with at least five.

The cluster is Angi-proof not because of any specific copy on any specific page, but because Angi's business model is structurally incompatible with each of the three commitments. They would have to become AskBaily to copy it. If they became AskBaily, they would stop being Angi.

The accounting

The transparency cluster is three pages, roughly 1,300 lines of TypeScript and MDX combined. The engineering effort was small. The ongoing effort — keeping /roadmap current within 72 hours of every ship, keeping /reviews updated as new projects close, keeping /commitments honest against actual operational behavior — is what makes it expensive. That expense is the moat.

Every wave since Wave 167 has had a /roadmap update as part of the ship checklist. Every closed-won project has a homeowner-permission request for /reviews inclusion as part of the close-out flow. Every deviation from a /commitments line triggers an internal incident review. The cluster is not static; it is an operational posture.

The posture is why the blog exists. Every shipment is recorded. Every commitment is dated. Every review is attributable. When a homeowner asks, in 2028, whether AskBaily is still the same company that promised transparency in 2026, they can read the record and decide for themselves.