The short answer
Build the system before hiring the team, in the order set out below. In that order, one focused operator can run outbound for a whole startup.
What an outbound sales engine is
An engine produces qualified conversations with buyers who were not looking, on a schedule rather than by luck. A campaign is a burst of activity that ends. An engine compounds, because every send shows what the market responds to. For a pharma startup this matters more than usual. Its credibility is scientific, its claims are regulated and its buyers punish sloppy outreach.
The build order
- Define one buyer, with one title, in one segment, and one problem the product solves, and if ten real companies cannot be named, the profile is too loose.
- Build a verified data layer, because bad data does double damage in pharma, since bounces hurt deliverability and a mis-targeted clinical claim is a compliance problem.
- Protect the domain before the first send, with cold outreach from separate domains, warmed for weeks, at low volume per mailbox, because the corporate domain carries investor, regulator and partner mail.
- Write for one real person, on approved claims, in short, plain words specific to the buyer's problem.
- Add LinkedIn alongside email, with the same buyer and message logic, from the founders' and sellers' own profiles.
- Route replies fast, because an interested reply goes cold in hours, so a founder or seller picks up every warm conversation the same day, logged in the CRM.
- Measure qualified conversations, meetings booked and attributed pipeline weekly, rather than sends.
The mistakes that kill pharma outbound
- Sending cold from the corporate domain, which damages every email the company sends afterward, investor and regulator mail included.
- Buying a cheap list and sending one template to all of it.
- Pitching the science first, when buyers reply to their problem stated plainly and then ask about the science.
- Treating compliance as a later problem, rather than agreeing claim boundaries before the first sequence.
- Hiring reps before the system exists, so they spend the week prospecting by hand.
- Quitting at week three, while the engine is still calibrating list, message and market.
Build it in-house, or buy the build
Everything above can be done in-house. The costs are time and tuition, in tooling, the deliverability learning curve, data sourcing and months of founder attention away from the science and the fundraise. A startup with a technical founder and no urgent revenue pressure may reasonably build its own. The alternative is a partner that builds in the company's name, proves the engine on live numbers and hands it over with a trained operator and a documented playbook.
How long does the build take?
The infrastructure takes weeks. Domain warmup alone takes a few weeks before any cold sending, and with warmed assets first conversations can land in the first weeks live. Repeatable results typically take a few months of live iteration.
Enquirer builds and hands over outbound engines of this kind through its sales and go-to-market practice.