Milestone-based delivery
Our delivery milestones will provide clear acceptance points and opportunities to continue or exit.
Campaign-ready lists, with fixes that last
We propose a tool to prepare the right audience, explain who was left out and return approved corrections through a method agreed with Massey IT.
Our delivery milestones will provide clear acceptance points and opportunities to continue or exit.
User experience design is a key differentiator for BrightDesk. We will design the tool so your team can understand what changed, assess their options, and decide what to do next.
We will use AI-driven development to support prototyping and iteration. Any deployed AI and use of customer data must meet Massey’s IT and governance requirements.
Our team will compare direct-mail and email results with your current process, checking who should be included, who should be left out and why.
Your team will initially review recommendations. We will introduce automation only after observed use demonstrates that the underlying process is reliable.
Our team brings experience across a variety of organizations, including work supporting an organization with more than 4,000 employees nationwide.
These principles guide how we would link records, review decisions and prepare each campaign.
We will keep contact restrictions tied to the right person and channel. Unclear cases will go to review, and our checks will include eligible customers removed by mistake.
We will preserve original records and explain each match, change and exclusion. Reviewers will be able to question a result and undo a mistaken link.
We will preserve approved corrections across new exports. The tool would track which changes reach the CRM and flag failures or conflicts with new information.
Follow a contact correction from review to the next export and a CRM update. All records and update results are fictional; nothing leaves this demo.
The proposed steps, shown with the same fictional records
Our team will compare equivalent campaigns before and during the pilot. We will agree targets with Massey after measuring the current process.
| Measure | What to compare |
|---|---|
| Less cleanup | Time spent preparing lists and reviewing exceptions |
| More accurate audiences | Duplicates, unsuitable inclusions and eligible customers removed by mistake |
| Fewer repeat fixes | Corrections repeated after new exports; CRM updates confirmed or still unresolved |
| Fewer campaign delays | Campaigns held up by list problems and the reasons for those delays |
Our team will estimate value with Massey using measured improvements and the costs they provide.
The approved audience in the mail-house or email-platform format, with contact and eligibility checks before release.
The report would show who was removed, at which step and why, keeping every applicable reason while counting each removal once.
The tool would track CRM updates as reviewed, submitted, confirmed or failed, with source confirmation required before an update is complete.
| ID | Capability | Expected behavior |
|---|---|---|
| FR01 | Check incoming files | The tool would report missing fields or incomplete files before using them. |
| FR02 | Link records carefully | The tool would keep people, households, properties and accounts distinct, with original IDs and reversible links. |
| FR03 | Prepare a campaign | The tool would use saved rules and available current service, property and sales information. |
| FR04 | Respect restrictions | The tool would honor person, channel and Do Not Merge rules and hold unclear cases for review. |
| FR05 | Remember corrections | The tool would retain approved changes across exports and flag conflicting information. |
| FR06 | Explain exclusions | The tool would show all reasons, count each removal once and let reviewers inspect mistakes. |
| FR07 | Support review | The tool would show evidence and record who approved, changed or rejected a suggestion. |
| FR08 | Release usable files | The tool would recheck the audience and produce the approved mail or email format. |
| FR09 | Confirm CRM changes | The tool would track reviewed, submitted, confirmed and failed updates through a supported method. |
| FR10 | Support the team | Our team will provide agreed access and monitoring, with handoff details decided together at that stage. |
Our team will work with Massey IT to choose hosting, access controls and data handling. Together, we will confirm how ServSuite and the Lead Log can supply the records needed for each campaign.
We will agree with Massey IT which corrections belong in which fields and test the supported update method. If direct integration is unavailable, we will assess a controlled import or IT-managed update. The tool would retain the original value and change history.
The demonstrated fields include Do Not Telemarket, Do Not Merge, Do Not Market: Mail and Do Not Market: Email. Our team will confirm their meaning and the treatment of deceased information with Massey.
Our team will work with IT to agree on secure transfer, storage, retention, backups and access. We will obtain approval before any outside address or AI service receives customer data.
Our team follows a structured software development life cycle (SDLC). We will work through these phases with Massey's marketing and IT teams, using agreed review points to decide when the work is ready to progress.
Our team will map campaign workflows, source files, requirements, scope and access.
Acceptance point We will agree priorities with Massey.
We will design linked customer records, campaign workflows, architecture and the review interface.
Acceptance point Marketing and IT will review the design.
We will build a working prototype and refine the agreed campaign and correction features.
Acceptance point We will demonstrate the agreed functions.
We will test completed mail and email campaigns, file formats and supported CRM updates.
Acceptance point Marketing and IT will review results and approve readiness.
Our team will configure agreed integrations and carry out a staged rollout and handoff.
Acceptance point Massey will approve production use after the agreed checks.
We will provide any support, fixes and improvements agreed with Massey.
Acceptance point We will review agreed changes and results with Massey.
BrightDesk and Massey will agree each milestone's deliverables and acceptance criteria and review progress before proceeding. Automation will require proven process reliability and approval.
Our team will review the campaign steps with marketing, including the exceptions experienced staff know. We will work with IT to confirm the sources, fields and ways to return corrections.
Our team will run one completed direct-mail campaign and one email campaign through the proposed workflow. We will compare the results with the existing process and investigate differences against the agreed rules; the old list is a comparison, not assumed to be correct.
Our team will agree on responsibilities with Massey before handoff.
| Team | Responsibility |
|---|---|
| Marketing | Campaign rules, exception review and approval to release each list |
| IT / BI | Source access, CRM updates, monitoring and support |
| Operations | Service and property eligibility, including offers already in progress |
BrightDesk and Massey will agree on the full handoff details later in the project, including what Massey will receive to operate the system without relying on BrightDesk after rollout. We will adjust the rollout based on observed reliability, addressing errors before expanding use.
This proposal focuses on the product and how our team would deliver it. If Massey would like to explore it further with BrightDesk, we will discuss pricing in a follow-up meeting.
Reusable functionality. Our team will retain the right to reuse, package and commercialize general-purpose components and functionality. This reuse will exclude Massey's data, branding and confidential information.
Delivery and handoff. BrightDesk and Massey will agree on the full handoff details later. The final agreement will define what Massey receives and its rights to operate and maintain the solution independently, BrightDesk's reuse rights, and each party's responsibilities.
Any later lead-ranking work or CRM replacement would be a separate decision.