Positioning AskBaily as a platform, not a product

AskBaily has been pitched so far as a product homeowners use to find contractors. Wave 221 is the shift in how we describe ourselves publicly. We are a platform. Three partner surfaces went live at /partners/affiliate, /partners/integrate, and /partners/nonprofit, each aimed at a distinct partner type with distinct economics and distinct expectations. This post is why the positioning matters and what the three programs actually offer.

The three partner surfaces

/partners/affiliate is aimed at content creators, publishers, and influencers in the home-improvement, real-estate, and personal-finance categories. The program offers a per-closed-won commission to affiliates who refer homeowners to AskBaily, tracked via a dedicated affiliate-code parameter and paid on a monthly cycle. The page lays out the commission structure transparently: a flat dollar amount per closed-won project, not a per-click or per-signup bounty. The flat-dollar-per-closed model is deliberate; it aligns the affiliate's incentive with homeowner success, not with volume pumping.

/partners/integrate is aimed at developers and adjacent platforms — CRM providers, home-services software, real-estate platforms, and any third-party system that wants to embed AskBaily's contractor-verification or contractor-matching capability. The page documents the public API surface: the /api/verify endpoint, the /api/match endpoint, the /api/scope endpoints, and the webhook events that notify partners when a project closes. The documentation is maintained as an OpenAPI v1.1 specification published at /data/openapi-v1.1.json.

/partners/nonprofit is aimed at housing-assistance nonprofits, fire-rebuild organizations, senior-home-services nonprofits, and similar organizations that serve homeowners needing remodel or repair work. The program offers AskBaily's contractor-matching and verification capabilities at no cost to qualifying nonprofits, with the expectation that the nonprofit routes its homeowner clients to our pre-verified pro pool rather than to a generic "contractor referral" list. The page explains eligibility, onboarding, and the operational expectations of a partner nonprofit.

Why "platform," not "product"

The positioning shift matters because the three partner programs imply a multi-sided surface, not a single homeowner-facing product. A platform has distinct audiences, distinct APIs, distinct commitments to each audience, and a strategic interest in serving every audience well because the economics only work when the sides balance.

A product has one customer. The two framings produce very different engineering decisions. A product-framed AskBaily would invest every engineering hour in the homeowner chat surface. A platform-framed AskBaily invests in the contractor onboarding rail, the integration API, the nonprofit admin panel, and the homeowner surface, in parallel. Wave 221 is the explicit statement that the platform framing is where we are now.

The shape of the affiliate program

The affiliate commission is a flat $200 per closed-won project, paid monthly. There is no per-click, per-signup, or per-lead bounty. Affiliates receive a unique code (ref=XXXXXX) that attributes referrals. A referral converts to commission only when the referred homeowner completes a project and pays their contractor through our close-out rail. The flat-closed commission is designed to attract affiliates who care whether the homeowner actually benefits, which is a different selection than a per-signup bounty attracts.

The program has no affiliate minimum. Any creator or publisher can sign up through the /partners/affiliate page, get a code, and start referring. The page documents the monthly payout cycle, the close-tracking methodology, and the appeals process for disputed attributions. Transparency on the program terms is a platform commitment.

The shape of the integration program

The integration surface is the public API at /api/verify, /api/match, /api/scope, and the webhook events attached to close, dispute, and scope-change. The API is documented as OpenAPI v1.1 with request and response schemas for every endpoint. Rate limiting is documented. Authentication is via API key with per-partner scopes. The full documentation lives at /partners/integrate/docs.

The integration program targets partners like CRM providers, real-estate platforms, and home-services software. A real-estate platform selling a house in a pre-rebuild state can offer AskBaily's contractor-verification API as a homebuyer trust feature. A CRM platform serving contractors can offer AskBaily's match-intake API as a feature that lets their contractor customers accept pre-verified homeowner leads. The API surface serves both cases with the same endpoints and the same authentication.

The shape of the nonprofit program

The nonprofit program is the most operationally involved of the three. Qualifying nonprofits receive access to AskBaily's contractor pool and verification rail at no cost, but the program requires onboarding (verification of 501(c)(3) status, service-area alignment with AskBaily coverage), ongoing reporting (volume of homeowner referrals, outcome tracking), and a written agreement about how the nonprofit represents AskBaily to its homeowner clients.

The population served — seniors on fixed incomes, fire-rebuild families, housing-assistance recipients — is often the most vulnerable to contractor fraud and hardest to help through traditional contractor-referral channels. The nonprofit program is designed to serve that population directly by bypassing the lead-brokerage layer entirely. Nonprofits route their clients to a pre-verified pool; AskBaily verifies; the contractor delivers.

What this tells homeowners

The platform framing does not change the homeowner experience. Homeowners still hit the same /chat, get matched with the same verified pool, close projects through the same rail. What the partner surfaces add is a visible statement that AskBaily's business model is not single-sided and is not extractive. Affiliates get paid only when homeowners succeed. Developers integrate against a documented API. Nonprofits serve their clients for free. The three partner surfaces are, together, the demonstration that the platform's incentives are aligned.

What Angi and Thumbtack cannot copy

They have partner programs. What they do not have is a platform positioning that matches their revenue model. Angi's economics depend on contractors paying per lead, not on external partners extending their reach. Thumbtack's integration API exists but serves contractor-adjacent tools, not homeowner-facing partners. Their platform framings, where they exist, are thin.

Ours is substantive because the three partner programs are substantive. Each has a documented economic structure, a public page, and a commitment to maintain it. The commitment is what distinguishes a platform from a marketing slogan.