Delivered engagementSaaS & Infrastructure · $25k – $35k
TRES

jointres.co

Delivered engagement. Coralsoft designed and built this product end to end; figures below retain their evidence level.

WebBackendNext.jsReactLoops + React Email
tres-community-intelligence.example / dashboard
TRES Deep Discovery report — ranked communities with reach, engagement and fit-score over a 924k aggregate audience
The situation

What was in place before we started.

A B2B SaaS platform connecting brands with communities — built end-to-end as a monorepo with a real-time Convex backend, a hybrid AI search engine across 85,000 communities, Stripe partnership payments, and a Shopify affiliate app.

Brands running community-led growth face a research problem: there are tens of thousands of relevant online and offline communities — running clubs, wellness groups, professional networks, subcultures — but no structured way to find, evaluate, and partner with them. The process was manual, slow, and impossible to scale.

TRES was built to solve this end-to-end: discover communities by describing what you need in plain language, evaluate fit with AI-generated scores and reasoning, initiate partnerships with structured workflows and escrowed payments, measure the resulting social performance, and attribute revenue through an affiliate commerce layer. Coralsoft was responsible for the entire product engineering surface — architecture, Convex backend, all frontends, ingestion pipelines, LLM enrichment, Typesense search, Chrome extension, Shopify app, and admin tooling — evolved continuously as the corpus grew from 3,000 to 85,000 communities.

Constraint

One platform from research to ROI — meaning six product surfaces had to share a single source of truth without leaking auth, drift on schema, or duplicate logic. The backend boundary had to stay clean as new product surfaces were added every quarter.

Timeline
6 months reconstructed
Team
5 people reconstructed
Budget
$25k – $35k reconstructed
Platforms
2
Stackrecorded
Next.jsReactLoops + React EmailWXT (Chrome ext)Convex (backend + realtime)TypeScriptTypesense hybrid searchAnthropic Claude (Sonnet + Opus)OpenAI embeddingsClerk authStripe Connect + CheckoutShopify App BridgeInsightIQ / PhylloApify + Bright DataCloudflare R2dub.coPlaywrightpnpm monorepo
Challenges

Each constraint, and what we did about it.

Constraint

One platform from research to ROI — meaning six product surfaces had to share a single source of truth without leaking auth, drift on schema, or duplicate logic. The backend boundary had to stay clean as new product surfaces were added every quarter.

What we did

Convex is the system of record for all product data, auth-aware APIs, scheduled jobs, and long-running orchestration. Frontends never call third-party APIs directly for sensitive operations — everything is mediated through typed Convex queries, mutations, and actions. This keeps the security boundary clean and makes the backend the single source of truth across six product surfaces.

Results

Outcome, with the source of every figure.

85K
Enriched research communities in the production corpus
self-reportedCoralsoft's own figure for its own delivery, stated in cases.ts. No third-party attestation in the sources.
28×
Corpus growth during the Coralsoft engagement
self-reportedCoralsoft's own figure for its own delivery, stated in cases.ts. No third-party attestation in the sources.
6
Distinct product surfaces sharing one typed backend
self-reportedCoralsoft's own figure for its own delivery, stated in cases.ts. No third-party attestation in the sources.
Showcase

How the system fits together.

4 of 4 views
tres-community-intelligence.example
TRES Partnerships dashboard with kanban columns from Outreach to Completed and per-community EMV
tres-community-intelligence.example
TRES social measurement view for the Sirius Club ambassador campaign with EMV, engagement rate and per-community feed
tres-community-intelligence.example
TRES — product screenshot
tres-community-intelligence.example
TRES — product screenshot
Roadmap

How it was sequenced.

6 monthsreconstructed delivery
Weeks 1–4

Discovery & architecture

Deep Discovery, partnerships kanban, social measurement and Stripe payouts in a unified workspace — the day-to-day surface where research becomes revenue.

  • Brand portal
Weeks 5–13

Core build

Corpus management, enrichment ops, custom discovery reports and EMV rate cards.

  • Admin console
Weeks 14–18

Integrations & data

Embedded affiliate links, per-community discounts, webhook-based order attribution, and the full pending → approved → paid commission lifecycle.

  • Shopify app
Weeks 19–23

Hardening & QA

One-click community capture from Instagram, Facebook, Luma and Meetup.

  • Chrome extension
Weeks 24–26

Launch & handover

Apify + Crawlee + Playwright pipelines for Luma and Meetup ingestion, feeding the enrichment queue alongside Bright Data Instagram imports.

  • Scraper fleet

More work like this.

Every case study is a Coralsoft delivery story, with the evidence behind each figure kept visible.