Kontraktr™

Why use it

If you're already running your shop on Kontraktr, every Prospektr™ lead that converts into a real customer should live in Kontraktr's customer database — that's where you'll quote, invoice, and produce against. The integration removes the CSV double-entry between the two products.

Available on every Prospektr plan — no tier gate. We want both products to feel like one workflow.

Requirements

• An active Kontraktr workspace (any plan)
• A Kontraktr integration API key (one-time setup, see below)

Setup

1. In Kontraktr, generate an integration API key. (For now this is via node scripts/mint-integration-key.mjs --tenant-slug=<slug> --name="Prospektr" run by your Kontraktr admin. A self-serve UI is on the roadmap.)
2. Copy the plaintext key (shown exactly once at creation time). It looks like kk_live_a1b2c3....
3. In Prospektr, go to /app/settings/integrations.
4. Enable the Kontraktr (sister product) card at the top. Paste the API key and your Kontrol workspace ID. Save.

What gets created

For each new qualifying prospect, Prospektr POSTs to {kontraktrBaseUrl}/api/v1/customers with the prospect mapped to a new Kontraktr customer record:

• companyName — prospect business name
• contactName — same as companyName for v1; you can edit later
• email, phone
• address, city, state, zip
• notes — Prospektr classification metadata (segment, lead potential, reasoning, notable clients) appended for context.
• pricingTier — defaults to RETAIL; change inside Kontraktr.

Idempotency

Each Prospektr prospect has a unique prospektrId. The Kontraktr endpoint uses that ID (plus email match) to detect duplicates: if a customer record already exists for the same prospect, we update rather than create — you won't get duplicates if a prospect somehow gets re-pushed.