How I use Ektie to grow Ektie's own pipeline

Ektie's own B2B pipeline runs on Ektie. Morgan, the AI SDR, prospects every day. Orion, the Sales Director, reviews every cycle and writes coaching into persistent memory. Astra handles warm replies. I use the product on myself — which means I find out quickly when something doesn't work and I have first-hand data on what does.

What does Ektie's own outbound motion actually look like?

Morgan runs on 90-minute heartbeat cycles. Each cycle: pull new prospects matching the ICP (B2B SaaS founders and VP Sales at Series A–C companies, 20–100 employees, no dedicated SDR or a junior SDR still ramping). Research each account for a specific signal — hiring posts, recent funding, content they published. Write and queue personalised Step 1 emails. Log everything back to the CRM. I don't touch any of this. Orion reviews the output, writes coaching notes when something drifts, and those notes reload every cycle.

What do the numbers look like?

After 90 days with the ICP properly defined and Orion running weekly supervision cycles, Morgan's reply rate sits at 7.2% across sequences. Positive reply rate (expressed interest, not just "remove me") is 2.8%. Meetings booked per week from outbound: 3–4. Those numbers aren't magic. They're what you get when the ICP is tight, the research is real, and the coaching loop has had time to compound. Month 1 was 3.1% reply rate. Month 3 is more than double that.

What has using the product on myself taught me?

The ICP definition is everything. I had Ektie running for two weeks before I admitted my initial ICP was too broad — "B2B companies that need better outbound" is not a target, it's a hope. When I tightened it to founder-led sales teams with 20–100 employees who'd already tried manual outbound and stalled, the reply rate changed immediately. The second thing: Orion's coaching compounds faster than I expected. A coaching note written in week 3 is still shaping Morgan's output in week 12. The memory doesn't decay.

What does this mean for how I think about the product?

Building on your own product creates a useful forcing function. When something doesn't work, you feel it before a customer tells you. When something works well, you understand why from the inside. The most useful insight from 90 days of eating my own cooking: the supervision loop is the product. The agents execute well from day one. What makes them get dramatically better over time is the coaching cycle — the Director reviewing output, writing what worked and what didn't, and that knowledge persisting. That's not a feature. That's the architecture.