Portfolio V Sondea

Throw an idea. We'll tell you how big the market is in Colombia.

Sondea

Data · RUES · MCP · Substrate · Tech Lead · Deploy & Migration · Active · 2026-05-16+

Status

Beta · Substrate deploying

Sector

Data · RUES · MCP · Substrate

Operator

Harold Mideros · Tech Lead · Deploy & Migration

Site

Active · 2026-05-16+

The Receipts

Two surfaces. One product family.

300K

B2B records — RUES + Cyberleads + lawyer scrape · enriched and segmented

2

Surfaces — the user-facing product and the substrate underneath, one brand

MCP

Server live — Nexus reads via Model Context Protocol

8

Verticals segmented and queued for the Bite offer factory

A substrate without a name, and a product without a substrate.

FlowForge ran the lead ingestion, enrichment, segmentation and MCP server inside the substrate. Nexus read from it. Bite needed it. But it had no product surface — nothing to sell, nothing to point at.

Sondea (the product idea) was the right product — RUES-as-a-service for B2B: 'throw an idea, we tell you how big the market is in Colombia.' But the data layer underneath had a different brand.

On 2026-05-16, we merged them. Same product family, one brand.

Sondea is data. Nexus is decisions. Don't mix them.

Architecture principle · Brainz · 2026

Brand, then ground, then surface.

  1. I.

    Consolidated the brand.

    FlowForge (the substrate) and Sondea (the product) merged under the Sondea brand on 2026-05-16. sondea.co registered at DNSimple and added to DigitalOcean DNS the same day.

  2. II.

    Started the substrate extraction.

    Harold extracting the DB from the Mac Studio server → DigitalOcean managed databases. Nexus needs Sondea running in production with current segments before Bite can fish.

  3. III.

    Drew the verticalization map.

    AWS/GCP users → DO migration offer. WordPress → wedge offer. Colombian lawyers → LexPro. Property admins → Propi. Marketing teams → Amplifica. Enterprise B2B with sales teams → Command of the Message.

  4. IV.

    Parked the downstream products.

    Benchmarking-as-a-service, Credit Scoring API, Hidden Gems Fund — all enabled by Sondea's substrate. All parked until the Bite factory proves its first fish bite. Substrate first, product surfaces second.

The MCP surface Sondea MCP endpoint catalog · drop a doc screenshot or diagram
— image placeholder · drop a screenshot or photo here —

One brand. 300K records. Eight verticals queued.

  • 300K

    Leads enriched and segmented in the DB · RUES + Cyberleads + lawyer scrape

  • MCP

    Server live — Nexus reads lead-search, enrichment, segmentation primitives

  • 8

    Verticals segmented for the Bite offer queue · routed to specific Brainz surfaces

  • Product-surface launch sequenced after substrate stable + first Bite fish bite

What it runs on. Who runs it now.

  • Rails 7
  • MCP server
  • TusDatos
  • BigData (catastro)
  • Postmark
  • Action Mailbox
  • GPT-4 (email gen)
  • DigitalOcean managed DBs

— end of chapter V —

Harold Mideros

Operator · Sondea

Same loop. Your team next.

If this pattern fits your room, let's have a conversation.

A single discovery call. Then a written, scoped Companion engagement — or a clean no, with notes on what we saw.