Skip to content
Case Study · Platform · Live in production

Fair: a platform of 11 production AI products.

The maker tools makers actually want. Eleven products on one shared key, one billing line, one credit pool. E-sign, mail, CRM, forms, scheduling, support, decks, automation, link management, social, and data extraction.

Live across faircompany.ai with per-product domains. Unified API at api.faircompany.ai.

FairSign hero: Fair-Priced E-Signatures landing page on fairsign.ai.

Screenshot from fairsign.ai, captured 2026-05-06.

Section 01

The problem

Solo operators and small teams pay for SaaS that does not talk to itself. Mail in one tool. CRM in another. Forms in a third. Scheduling in a fourth. E-sign somewhere else. Each one is $20 to $50 a month. None of them share contacts, credits, or auth.

The fix the market keeps proposing is "an all-in-one." The all-in-ones bundle five mediocre products and charge $200 a month. The good standalone tools never integrate. The integration tools are a sixth subscription on top.

Fair is the third option. Eleven sharp products, each strong on its own, each priced fairly, all sharing the same identity, billing, and credit pool. Use one product or use all eleven.

Section 03

Three live products, screenshots from production

FairMail landing on fairmail.ai
FairMail · fairmail.ai
FairCRM landing on faircrm.ai
FairCRM · faircrm.ai
FairCrawl landing on faircrawl.ai
FairCrawl · faircrawl.ai

Screenshots captured 2026-05-06.

Section 04

The architecture

One Fair API at api.faircompany.ai sits in front of every product. Customers get one key, one billing line, and a single credit pool that draws down across products. A FairMail send and a FairCrawl scrape both metered against the same balance.

Each product owns its own domain (fairsign.ai, fairmail.ai, and so on) for branding and isolated UX, but shares auth, billing, and identity with the platform. New products plug into the same auth + billing rails without re-implementing them.

Standards live in a per-product convention: every product directory carries its own engineering, design, QA, and GTM agent definitions, so the platform team and product teams move in parallel without stepping on each other.

Section 05

Real outcomes

11

Distinct products in active build, each on its own production domain.

10 of 11

Product domains responding 200 in production at the time of this writeup (2026-05-06).

1

Shared API key, billing line, and credit pool across the entire platform.

$0.0007

FairCrawl public per-page extraction price.

4 surfaces

FairMail spans agent, transactional, marketing, and newsletter inside a single product.

0

External vendors required for the platform's email, CRM, forms, scheduling, e-sign, support, decks, social, automation, links, or extraction.

Customer counts, MAU, and revenue are private to Fair and not published here. These are the numbers we can stand behind in public.

Section 06

What is in flight

FairCrawl is shipping into the public 8-brand campaign. Per-product GTM is rolling out one product at a time. Landing pages, pricing, trial flows. Where two products overlap (e.g., FairSign on a FairForm submission), the wire-up uses FairFlow rather than a custom integration.

The platform is treating its own dogfood like a customer. Downshift uses Fair products inside its own portfolio. If a Fair product cannot survive its own portfolio's day-to-day, it does not ship.

Three more products (FairWrite, FairTrack, FairTable) are in build but outside the scope of this case study.

Want a platform of your own?

Downshift ships product, infrastructure, and platforms. Fair is what it looks like when the work is sustained over time.