by mkdirOne control plane for the whole estate.
Cold email fails at the infrastructure long before it fails at the copy, and it fails at the reply long after. Kriyo covers the whole run — from the DNS record to the opportunity — with one rule on top: a person is in the loop on every send.
Replies, one inbox and the pipeline
Every mailbox in one thread view. Each reply is classified, a response is drafted, and it waits in a queue until a person approves, edits or discards it. Interested replies become opportunities; out-of-office becomes a date; referrals become suggested contacts you can enrol.
Domains, mailboxes, warm-up and deliverability
The records that decide whether mail lands, per mailbox: MX, SPF, DKIM, DMARC. Warm-up age and staleness. Sender reputation. Inbox placement tests. A send-health check that says “no sends recorded in 26h” rather than “sending is broken”.
Campaigns, sequences, variants and results
Multi-step sequences with variants, a sending window in the client’s timezone, stop-on-reply, per-company limits, a do-not-contact list. Variants are compared weekly; a losing one is paused for you to look at, never rewritten. Results count people, not messages.
Prospecting and buying signals
Build a list by role, seniority, company size, industry and location. Searching is free; you spend only when you reveal a contact, and the cost is shown first. Signals bring in people when something changed: a new role, a funding round, a hiring push.
What you open in the morning, and what you open when something is wrong.
These are the screens as they ship. The names are the real names; the columns are the real columns.
| Screen | What it shows | What you do there |
|---|---|---|
| Today | A list, not a dashboard: what is waiting on you (a reply to approve, a DNS gate failing, an opportunity gone quiet), then what was handled for you. | Go to the thing that needs a person. When nothing does, it says so. |
| Replies | Queue, scheduled, history. Each queued reply carries the sent context, the inbound reply and a drafted response with a confidence tag. | Approve, edit, schedule or skip. Nothing leaves without one of those. |
| Inbox | Every mailbox in one thread view, triaged: needs reply, interested, question, objection, unclassified, no reply yet, handled automatically. | Read the whole thread in place, then reply from the mailbox that started it. |
| Pipeline | Opportunities by stage with a heat score; the out-of-office board with return dates; suggested contacts and where each one came from. | Work the interested ones. Approve the enrolment of a referred contact, or don't. |
| Campaigns | Status, leads, sent, replied, reply rate. Inside: analytics, the builder, contacts, replies split into genuine and automated, senders, settings. | Launch, pause, resume. Edit steps and variants. Change the sending window. |
| Deliverability | Per domain and mailbox: reputation, warm-up age, placement, sent today against the cap. A stall warning when sends stop being recorded. | Run a placement test. See which mailbox is holding the estate back. |
| Prospecting | Saved searches with their filter groups, the sources that are connected, and what a reveal will cost before you run it. | Search for free. Reveal when you mean it. |
| Audience | Sourced, contacted, replied, suppressed. The lead table with status and last activity. | Import from a file or a sheet; keep the do-not-contact list current. |
| Results | People contacted, people who replied, reply rate, interested. Reply rate by campaign. Where replies went. No open rate when tracking is off. | Export a CSV or share a report. |
| Setup | A getting-started checklist, the reply agent's approval rate and sent-as-written share, the account's sending window, credits, files and audit log. | Finish the checklist. Every action, who did it and when, is in the log. |
Send without you, or make up a number.
Both rules are enforced in the build. The front page explains each of them; the security page lists how each is held.
Nothing sends itself
No scheduled job can reach a send path. Every reply that goes to a real person was approved by one.
RULE TWOA number we don’t have is never a zero
Untested, unmeasured or unsynced renders as a dash and says why. Nothing is averaged into existence.
ISOLATIONOne database per client
Not a client column. A separate database, so one client’s data has nowhere to leak to.
Ask for a workspace of your own.
Invite-only for now. Tell us about your outbound and we’ll set you up. The checklist walks you from a verified email to a first campaign.