Productized vs custom: should you buy Beat or build a custom engagement?

Beat is a productized client surface that ships with every IG Local Business engagement. It pulls in Yelp, Google Analytics, GBP, and Local Falcon data, and writes a Monday briefing in plain English. It is opinionated software. The features are fixed because the opinion is the product.

A custom engagement is the inverse. IG operators show up, audit the bottleneck, and build whatever the bottleneck requires. The deliverable shape is decided after the diagnostic, not before. The price is the cost of senior operators for the engagement window.

Most B2B operators ask the question wrong. They ask "do we buy or build" as if those are mutually exclusive. They are not. The right question is "which parts of the engagement are productized, and which parts are custom".

When Beat is right

You operate a local business between 1 and 30 locations. You need a Monday-morning briefing that tells you what moved last week and what to focus on this week. The data sources are the standard local-business stack (Yelp, GBP, GA4, Local Falcon). The briefing is written in your voice. The dashboard sections are the same five every week.

If that description fits within 80 percent, you should be on Beat. The remaining 20 percent gets customized inside the engagement (custom briefing tone, additional data source, location-specific overrides) but the spine is shared with every other Beat client. The cost is predictable. The setup is fast.

When custom is right

Your data stack is not the standard local-business stack. You run a B2B SaaS at $30M ARR, your CRM is Salesforce, your warehouse is Snowflake, and your marketing-ops are in Marketo. Beat does not connect to that stack out of the box, and forcing it would compromise both the product and the engagement.

Or: your buyer is not a local-business operator. You need a different surface entirely. Next Best Action is the productized version for that buyer type. Custom is the path when neither productized option fits.

Or: the engagement is a one-time intervention. AI Adoption Sprint. Marketing-ops rebuild. Revenue-ops audit. Productized surfaces are weekly recurrence; sprints are time-boxed and end with a handoff. The economics flip.

The decision tree

Ask three questions in this order.

First: do you run a local business? If yes, Beat is the right surface. If no, productized Beat is not the answer and we should be talking about Next Best Action or a custom build.

Second: is the engagement recurring or time-boxed? Recurring engagements benefit from a productized surface because the recurrence amortizes the surface's development cost. Time-boxed engagements (Sprints, audits, rebuilds) end too early to justify a productized surface; they justify the operator time directly.

Third: are your data sources standard for the productized option? Beat connects to Yelp, GBP, GA4, Local Falcon. NBA connects to Salesforce, HubSpot, GA4, Google Ads, Meta Ads. If your stack is outside the standard list, the productized version requires custom integration work. Sometimes that is fine. Often the right answer is a custom engagement where the integration work IS the deliverable.

Why the false dichotomy persists

Most agencies sell custom because hours-billing rewards it. Most SaaS companies sell productized because per-seat pricing rewards it. The operating-company model lets us sell whichever shape actually fits the buyer.

The honest answer in 80 percent of conversations is "you want Beat for the recurring view, and you want a custom engagement to set up everything Beat sits on top of." Beat without the underlying rebuild gets you a working surface on top of broken plumbing. A custom rebuild without Beat gets you a fixed system you cannot see in real time. Both together gets you what you actually wanted.

That is also why Beat ships with every Local Business engagement instead of as a standalone purchase. The productized surface and the custom engagement do not compete. They compound.