How we work
Different work, the same rules
Campaigns and builds follow their own steps. Both start by agreeing what good looks like, and end with work you can check.
How a campaign runs
Scoping call
Your audience, the qualification level you need, channels and how leads reach your CRM.
Output: Scope notes
Agree the spec
Lead definitions, required answers and rejection reasons. You approve them before launch.
Output: Lead spec you approve
Pilot batch
A first, small delivery reviewed against the criteria before volume increases.
Output: First leads, with answers
Delivery
Leads arrive in your CRM or file with the answers and source behind each one.
Output: Leads in your CRM
Review and adjust
Accepted and rejected leads are reported with reasons; criteria are tuned with you.
Output: Report with rejections
How a build runs
Discovery
Users, workflows, existing systems and constraints, written up as scope and a milestone plan.
Output: Discovery plan
Design
Flows and key screens you review and approve before building starts.
Output: Key screens
Build in milestones
Each milestone has written acceptance criteria: what it includes and how it is tested.
Output: Working staging build
Test and accept
A staging demo per milestone. Defects are logged with severity and fixed.
Output: Acceptance report
Launch and handover
Deployment, documentation and access handed over. Support terms are set in your statement of work.
Output: Code, docs and access
Agreed before we start
What a good lead or a finished stage looks like, settled before anyone is contacted or any code is written.
Work you can check
Leads with their answers; milestones on staging.
Ownership settled up front
Who holds the data, code and accounts, agreed before work starts.
One point of contact
Regular written reports, and problems raised early.
What you approve before work starts
For a campaign
- Target audience and account list rules
- Lead level and qualification questions
- Rejection reasons and how disputes are handled
- Delivery format, CRM fields and reporting cadence
For a build
- Scope, users and the workflows in and out of scope
- Milestones and their acceptance criteria
- Systems to integrate and the data that moves
- Launch, ownership, handover and support terms
Not every lead is ready to buy
We agree which level you are paying for before launch, so a content download is never sold as a sales-ready opportunity.
See the full definitions- 01
Content-engagement lead
A person who matches your ICP and asked to receive one of your assets. Contact details are checked and the opt-in is recorded.
Not: Not a request to speak to sales. Most need nurture.
- 02
Marketing-qualified lead (MQL)
A content-engagement lead that also meets rules you set, such as acceptable answers to your questions or a match to a target account.
Not: Budget, authority and timing are not yet confirmed.
- 03
BANT-qualified lead
A lead whose budget, authority, need and timing were each confirmed in a live conversation and recorded.
Not: Not a booked meeting.
- 04
Appointment (held meeting)
A BANT-qualified prospect who accepted a meeting with your rep and attended it, with a briefing note.
Not: A booked meeting that did not take place. No-show rules are set in your statement of work.
When a lead can be rejected
Reasons are agreed before launch. The dispute window and the remedy, such as a replacement or a credit, are set in your statement of work.
- Outside the agreed audience or persona
- Invalid or bounced contact details
- Duplicate of a record in your CRM, suppression list or an earlier delivery
- Missing a required qualification answer
- No consent or opt-in record where the campaign requires one
- Meeting no-show, as defined in your statement of work
What reports show
A weekly delivery report and a monthly review are the proposed default; your cadence is set in your statement of work.
Campaigns
- Leads delivered, accepted and rejected, with the reason for each rejection
- Meetings booked, held and no-show for appointment programs
- What prospects are saying, and what changes next period
Builds
- Milestone status against its acceptance criteria
- Open defects by severity, and what was fixed
- Decisions needed from you, and what comes next
Data and compliance
- Data sources and the opt-in method for each campaign are documented in your statement of work.
- Suppression lists are applied before launch, and opt-outs are honoured for the rest of the campaign.
- Access to your systems and data is limited to what the work needs and returned at handover.
Put your criteria in writing
Tell us about the campaign or the build. We scope it on a call and send criteria and terms in a written proposal.
Planning a campaign? Start with your audience and the lead level you need.
Discuss your campaignPlanning a build? Start with your users and what it must connect to.
Discuss your buildPrefer email? hello@rdcsgenix.com