Built by an outbound agency that got tired of guessing.

mkdir runs cold outbound for clients. Kriyo started as the thing we built to run it: one place for a client’s domains, mailboxes, warm-up, sequences and replies, with the client able to watch it happen.

Two things kept going wrong with the tools we used before. Replies went out that nobody had read, under a client’s name. And dashboards showed green figures for things that had never been measured, which is how a sending estate burns quietly over weeks.

So the engine has two rules that are enforced in the build rather than promised in an onboarding call. Nothing sends without a person. A number we do not have is never a zero. Every other decision follows from those two.

It is being opened, by invitation for now, to anyone who runs outbound — for themselves or for clients — and wants to keep the decisions.

How we work

• Each client is a separate database, because we ran several and did not want to find out the hard way what a shared one does.
• What is true of the product is written down in architecture records, and this site is written from them.
• Example data on this site is labelled as example data. There are no testimonials here because we have not asked anyone for one.

mkdir’s own site is mkdirhq.com. To reach the people who build this, use the contact page.