Skip to content

Worked example: Kigentic

VOLATILE. This content is expected to go stale; regenerate quarterly or when the venture changes. It is a worked example of venture ownership, not a durable rule.

A real instance of venture ownership: the Kigentic build — shipped as Nextgentic (nextgentic.de) — run under Niccolò, requested by Sebastian.

What Kigentic is

A pitch Sebastian forwarded: an AI and automation expert marketplace for DACH, targeting SMEs that need n8n, Make, AI agents, chatbots, CRM automation, and workflow automation. The founder claimed 3.5M SMEs need experts, an MVP existed, and the ask was 150k for 12.5%.

The strategic read

Relevant to SCAILE/CITO — but only framed as lead-gen / demand-capture, not a marketplace.

  • A broad AI-expert marketplace is hard and slow to make liquid.
  • A demand-capture portal around concrete AI-automation problems is highly relevant.
  • SCAILE can use content and GEO to capture buyer intent: "best n8n agency", "AI agent for invoice processing", "Make automation consultant Germany", "AI chatbot agency DACH", and so on.
  • Leads route to qualified vendors, CITO, or internal SCAILE offers depending on fit.
  • The core asset is not marketplace software — it is demand capture: landing pages, intent content, lead forms, qualification, routing, and follow-up.

What it is not

Not a generic marketplace, a directory of random AI freelancers, a broad agency listing, or a software platform before demand is proven.

First principle: capture high-intent SME automation demand first, match manually, build product only after the lead flow proves where the money is.

First MVP

  1. Landing page for SME AI-automation problems.
  2. Category pages: n8n, Make, AI agents, AI chatbots, CRM automation, invoice automation, customer-support automation, marketing/sales automation.
  3. Lead form: "Tell us what you want to automate."
  4. Vendor/expert intake form.
  5. A Google Sheet or CRM pipeline for leads and vendors.
  6. A content plan for high-intent SEO/GEO pages.
  7. Manual matching before any marketplace logic.
  8. Slack or email notification on every new lead.

Operating line for this build

  • Primary guide: Niccolo.
  • Strategic owner: Simon.
  • Venture / context input: Sebastian and/or Anton, depending on the project.
  • Working source of truth: the Kigentic working sheet, until Niccolo says otherwise.
https://docs.google.com/spreadsheets/d/1xbUL2ikwLVpyz41JwlhU_lvRLzXTHYWmZ49HTf7E7tY/edit

Can't open it? Ask Niccolo for access.

Lessons from this build

This was a first FA project, and the early friction is now baked into the FA onboarding guide. The durable lessons:

  • "Kigentic" was the brief's codename, not the venture name — it shipped as Nextgentic. A brief is a pitch to interpret, not a spec to ship verbatim — read it critically, restate the core task, and confirm the real name with your guide before building. See the briefing section.
  • Infra must be under scailetech from line one — GitHub, Vercel, Supabase. No personal accounts; request access on day 1 if missing. See vercel-render-supabase.md.
  • Confirm the target-market language during briefing. A German/DACH venture needs someone who can write and judge German. Flag any gap on day 0, not day 3. See the language rule.

Owner: Current FA Last reviewed: 2026-07-02