A gated asset, form and follow-up designed from what your sales team can act on, rather than from how many addresses the form can collect.
About this service
The answer first:
A gated asset is worth what the conversation after it is worth, so I build this backwards. Before deciding what the asset is, I listen to three recorded sales calls and read a quarter of closed-lost notes. Five to six weeks, one asset, one audience, one follow-up path.
What usually has to change first:
The asset. A checklist anyone could have written attracts people who download anything, and your team then works a list of readers. The asset that produces a conversation forces the reader to admit a specific situation: a renewal-cost teardown for teams already on a named vendor, an audit checklist for the inspection they are three months away from, a benchmark set narrow enough that they need to know where they sit inside it. If what you have is a generic PDF, I will say so, and the rewrite is part of the work rather than an upsell.
The form:
Arguments about field count are stale. The question is which field the follow-up actually depends on. If nobody routes, prices or writes differently based on company size, that field is decoration and it costs you completions. I keep the fields a rule can act on and delete the rest. Source parameters, gclid and fbclid are captured hidden and written to the record, so the first message can reference the thing the person came in from instead of greeting them as a stranger.
Delivery, and where India differs:
Email delivery is the default everywhere and here it is not enough. WhatsApp is where an Indian buyer reads. I build the opt-in as a separate, explicit choice on the form, deliver through the Meta Cloud API via Gupshup, Interakt or WATI, and submit templates for approval early, because approval takes days and teams find that out in the week they wanted to launch. Outside India the same slot goes to email plus a calendar link, and I do not pretend the two channels behave alike.
Consent, and why I am strict about it:
Under the DPDP Act you need notice at collection, a stated purpose and a withdrawal that works. Pre-ticked boxes and "by downloading you agree to receive communications" come out. Where the list carries real exposure, health status or financial position, I use double opt-in and accept the smaller list. A list you cannot legally mail in two years is not an asset.
The handoff:
The qualification rule is written as something your CRM can execute, field values and thresholds, not a paragraph in a deck. The first fourteen days of follow-up are written and sequenced. After that your team owns it, and I would rather hand over four touches you will actually send than thirty you will not.
Out of scope:
Paid media, purchased lists, sales training, CRM re-implementation, and gating a piece that should be public. If the asset needs to be found in search, putting a form in front of it costs more than the addresses are worth, and I will argue that before I build it.
I turn this down when:
Cost per lead is the only number on the table. A funnel optimised for cost per lead reliably produces cheaper leads and less pipeline, and if that is the measure you are held to internally, we will disagree by month two. Also declined: teams who want the asset written without giving me access to sales calls, and anyone who wants a lead volume figure committed in the contract.