Why We Integrate Instead of Build: The Howie Decision

When we decided referral intros needed scheduling built in, the obvious move was to build it. A booking link generator is a weekend project. Slot picker, availability rules, calendar write. Every product team has had this conversation, and most of them talk themselves into building.

We shipped an integration instead. It was the fastest integration we have ever delivered — and the reasoning behind that choice drives more of our roadmap than any single feature does.

But first, the personal part: I use Howie every day. Not just for Introzy referrals — for client calls, candidate interviews, rescheduling entire afternoons with one message. I wrote about that experience in detail in my other post, and the short version is that Howie quietly removed a problem I had stopped noticing was eating my time. When you genuinely love a tool, the integration conversation is different. It is not "should we partner with these people?" It is "we already use this, how do we make it two seconds for everyone else?"

Scheduling is a solved problem — by people who only do scheduling

The scheduling space is full of excellent, specialized products. Calendly defined the booking-link category and runs it at massive scale — their research shows 43% of professionals spend three-plus hours a week just scheduling. Howie took a completely different path — an AI secretary that negotiates times over email threads instead of sending a form, so the person on the other end often has no idea they are talking to an AI. Reclaim.ai optimizes your entire calendar around focus time and habits. Motion auto-schedules tasks alongside meetings. SavvyCal gives recipients a polished overlay of both calendars. Each of these teams works on scheduling all day, every day — time zones, recurring event edge cases, calendar provider quirks, no-show psychology, reschedule etiquette.

Any in-house version we built would be a worse product maintained by people whose actual job is referral infrastructure. I know this because I have used all of these tools. The depth they bring to scheduling is not something you replicate on the side.

The right question was never "can we build scheduling?" Of course we can. The question is: what do our users get from us that they cannot get anywhere else? The answer is referral tracking, attribution, and commissions — the connective tissue of a partner program. Every month spent maintaining a scheduling engine is a month not spent on the thing we uniquely do.

Make the stack you already have work together

Introzy's job is to make the tools you already use work together around your referral program. Your email, your calendar, your CRM, your scheduling assistant — we do not want to replace any of them. We want the referral to flow through all of them without anyone re-keying data.

That is why the integration catalog looks the way it does: HubSpot and Salesforce for CRM, Nylas for email and calendar, Slack for intake, Zoom for meetings, Howie for scheduling. The thesis is the same in every case — meet the tool where it is, take the thinnest path to value, and let the specialist be the specialist.

If you use Calendly and love it, great — keep using it and send your booking links in your intro emails. If you use Howie and want the scheduling to happen automatically inside the thread, we built that integration so you never have to think about it. We are not here to pick your scheduling tool. We are here to make the referral work regardless of which one you pick.

How we evaluated the Howie integration

Three criteria, in order:

Time to user value. From "user decides to try it" to "user gets value" — with Howie, that is pasting one email address into settings and checking a box on their next intro. Under a minute. No OAuth dance, no field mapping, no sync configuration. Nicole wrote a 60-second setup guide and it genuinely takes less time than reading it.

Integration surface honesty. Howie has no API — the product is conversational by design. Rather than treating that as a blocker, we asked what the thinnest honest integration was: CC him on the thread, let the existing calendar sync close the loop. Ale wrote up the architecture — we deliberately built no sync engine, no booking page, no scheduling logic at all.

Maintenance weight. No tokens to refresh, no API versions to chase, no webhook contracts to monitor. The integration is one database row per org and a CC line. When your integration has almost no moving parts, it almost never breaks.

Compare that to the build path: a scheduling engine is easy to prototype and brutal to operate. We would still be fixing time zone bugs today. And I say that as someone who has shipped calendar integrations — the edge cases are endless.

What this means if you are evaluating tools

There is a version of this post for buyers, not builders: beware of platforms that build a mediocre version of everything. The all-in-one pitch usually means a dozen C-minus features wrapped around one B-plus core.

The alternative pattern — a focused core plus honest integrations — means each tool in your stack is the best available for its job, and switching costs stay low because your data is not hostage to a monolith. Your scheduling tool should be chosen on scheduling merits — whether that is Calendly for booking pages, Howie for conversational scheduling, Reclaim.ai for calendar optimization, or something else entirely. We will meet it where it is.

Every feature you don't build

The Howie integration shipped in a fraction of the time our CRM integrations took, precisely because we refused to build anything Howie already does. That time went into the referral pipeline, commission automation, and the things nobody else builds for partner programs.

That is the compounding effect of integrate-over-build: it is not one saved month, it is a permanent reallocation of every future month. The best product decision is often the feature you decline to write.

For the specific problem the Howie integration solves — referral intros dying in scheduling limbo — read The Intro-to-Meeting Gap. And if you want to hear me gush about Howie for another 2,000 words, that post is here too.

See the integration philosophy in practice. Connect your stack — CRM, email, calendar, Slack, Howie — and let the referral flow through it. Start free →

Stop reading about referrals. Start tracking them.

Free up to 5 referrals a month. Every feature included. No card to start.