iConnect Growth Engine
Connect the steps between finding a prospect and winning the work
The iConnect Growth Engine is designed to coordinate a selected set of iConnect offerings into one agreed growth workflow, carrying evidence, engagement context and the next responsibility from research to marketing to sales, while each product keeps its own job and its own records.
Does this sound familiar?
Research finds a company, marketing runs a campaign and sales makes a call. Each team finishes its own task, but the context and the ownership fall into the gaps between them.
What it costs the business
Prospects are prepared twice, interested contacts go cold while nobody owns the next step, and leaders cannot see where the journey stalls.
Built for
- Chief executives and business owners who want one accountable route from research to revenue
- Commercial directors coordinating research, marketing and sales
- Sales leaders who receive hand-offs from marketing
From problem to gain
What changes when the work moves into one place.
The situation
- Prospects are prepared twice, interested contacts go cold while nobody owns the next step, and leaders cannot see where the journey stalls.
What your team does
- One agreed workflow
- Coordination, not duplication
- Step status for every run
What it produces
- An accountable path from research to engagement, opportunity and follow-up
- A named owner and a status for every step in the workflow
- Hand-offs that carry the evidence and engagement context with them
What you gain
- Fewer unclear hand-offs between research, marketing and sales
- Less repeated preparation
- A measurable route to suitable opportunities
The difference it makes
Fewer unclear hand-offs between research, marketing and sales
How
Each step in the agreed workflow is designed to name its owning product and the person responsible, and to show which steps are waiting.
Less repeated preparation
How
The evidence and engagement context are designed to travel with each hand-off, so the next team starts where the last one stopped.
A measurable route to suitable opportunities
How
Hand-off acceptance and the time between accepted stages are designed to be visible, so you can see where the journey slows.
How it fits together
What it does
- One agreed workflow
- Coordination, not duplication
- Step status for every run
What your team gets
- An accountable path from research to engagement, opportunity and follow-up
- A named owner and a status for every step in the workflow
- Hand-offs that carry the evidence and engagement context with them
How your team uses it
Commercial director
Agrees the growth workflow and which offerings take part
- Output
- A configured workflow with an owner for each step
- Next owner
- Growth team
Growth team
Reviews researched prospects and passes accepted ones on
- Output
- Reviewed prospects on the customer record
- Next owner
- Marketing team
Marketing team
Enrols consenting prospects in engagement and hands interested ones to sales
- Output
- A sales hand-off with its engagement context
- Next owner
- Salesperson
Salesperson
Accepts the hand-off and opens the opportunity
- Output
- A deal with its history, owned by a named salesperson
- Next owner
- Commercial director, who reviews the workflow
Inside Growth Engine
One agreed workflow
Designed as one workflow: discover, research, qualify, engage, convert and measure, with each step assigned to the product that owns it.
Coordination, not duplication
The Growth Engine is designed to own no customer data of its own. Each step would read and write through the owning product and link to that product's own screen.
Step status for every run
Each step is designed to show whether it is included, not yet set up or not included in your plan, so gaps are visible rather than hidden.
Hand-offs with a named owner
Enrolment in engagement and the hand-off to a salesperson are designed as explicit steps, each started by an authorised person.
Chosen components
A growth workflow may use iGrowth (Roadmap), iEngage (Roadmap), iConnect CRM (Controlled rollout) and Leads & Sales (iSales) (Controlled rollout), with workflow and measurement offerings added where they suit. You do not need all fourteen offerings.
How to start / What this requires
The Growth Engine is designed to coordinate the offerings you select, so it needs those offerings in place. A core growth workflow uses iGrowth (Roadmap), iEngage (Roadmap), iConnect CRM (Controlled rollout) and Leads & Sales (iSales) (Controlled rollout).
First step
Start with a tailored demoWe walk through your own workflow with you and confirm which of the requirements below apply to your team.
What needs to be in place
- The offerings in your agreed workflow, each at its own status. A step is only as available as the product that owns it.
- Customer records in iConnect CRM (Controlled rollout), where reviewed prospects and hand-offs are kept.
- Consent records and an email sending setup for the engagement steps.
- Authorised people to start each hand-off: the Growth Engine does not move a prospect on by itself.
What you gain by connecting it
Selected combinations, not every possible pair. Each connection shows how far it has been proven, so you can tell what has been shown working from what is still planned.
How to read the connection labels
- Demonstrated in testing
- Shown working in our testing, on code that is not yet released to customers.
- Configured per deployment
- Depends on setup for your deployment, such as a connected channel or approved knowledge.
- Planned
- Not built yet. Shown to explain the intended workflow.
Research into sales
The Growth Engine is designed to pass a reviewed prospect from iGrowth (Roadmap) to iConnect CRM (Controlled rollout), a consenting audience to iEngage (Roadmap) and an accepted hand-off to iSales (Controlled rollout), each through the customer record.
Works with
See the full workflowConnections
- iGrowthCRM
- Reviewed prospect
- Demonstrated in testing
- CRMiEngage
- Eligible, consenting audience
- Demonstrated in testing
- iEngageiSales
- Sales-accepted hand-off
- Demonstrated in testing
Coordinated enrolment and sales hand-off
The Growth Engine is designed to start the enrolment step in iEngage (Roadmap) and the hand-off to a salesperson in iSales (Controlled rollout), each started by an authorised person.
Works with
iSales (2)Controlled rolloutiEngage (3)RoadmapSee the full workflowConnections
- Growth EngineiEngage
- Coordinated enrolment step
- Demonstrated in testing
- Growth EngineiSales
- Hand-off to a salesperson
- Demonstrated in testing
Adding visibility work
Where iSEO & Outreach (Roadmap) is included, publisher relationships are designed to sit on the same customer record in iConnect CRM (Controlled rollout). So far this has been shown in database tests only.
Works with
CRM (1)Controlled rolloutiSEO & Outreach (13)RoadmapSee the full workflowConnections
- iSEO & OutreachCRM
- Publisher contact linked to the CRM
- Demonstrated in testing
Suggested solutions
Complete workflows this product takes part in.
Related pages
- iGrowth (12)Roadmap
- iEngage (3)Roadmap
- iSales (2)Controlled rollout
- CRM (1)Controlled rollout
Good to know
We would rather you knew the current limits before a demo than after it.
- Roadmap: the Growth Engine is not yet offered. Request a demo to book an executive growth-model session.
- It is not another prospect database or customer record: it coordinates the products that own those records.
- A step can only be used once the product that owns it is available to you, and most of those products are on the roadmap.
- It does not promise revenue, lead volume or return. Results depend on evidence, execution, offer and market.
- It does not move prospects on by itself: authorised people start each hand-off.
Technical details
For technical evaluators: records, roles, inputs and setup, as far as current evidence supports them.
Show the technical details
- Records
- The Growth Engine owns no primary record. Each step's record stays with the product that owns it.
- Hand-offs
- Enrolment and the sales hand-off are designed to be started by an authorised person and recorded once, so that a repeated request would not create a duplicate deal. That safeguard has not been released.
- Step status
- Each step is designed to show whether it is included, not set up or not included, and to link to the owning product's own screen.
- Delivery status
- Roadmap. The coordination design has been demonstrated in testing on demonstration data. Some steps, such as delivering follow-up notices, are not built yet, and nothing is released.
Questions and answers
Is the Growth Engine the same as prospect research?
No. Prospect research is iGrowth (Roadmap), which does one job. The Growth Engine coordinates several jobs into one workflow and carries context and responsibility between them.
Do we need all fourteen offerings?
No. You select the offerings that suit your workflow. A core growth workflow uses iGrowth (Roadmap), iEngage (Roadmap), iConnect CRM (Controlled rollout) and Leads & Sales (iSales) (Controlled rollout).
Does the Growth Engine store our customer data?
No. It owns no primary record of its own. Customer records stay in iConnect CRM (Controlled rollout), and each step's data stays with the product that owns it.
Does an enquiry count as marketing consent?
No. An enquiry is never marketing consent. Engagement is designed to enrol only consenting contacts.
Is the Growth Engine available now?
No. It is on the roadmap. Request a demo to book an executive growth-model session.
Book an executive growth-model session
Tell us how research, marketing and sales hand work to each other today. We will reply to arrange a tailored session.