MBP operates a structured eight-step engagement workflow. Nothing is started without a written scope. Nothing is delivered without a confirmation record. Every client file is maintained in full — from first inquiry to final report.
Client Workflow
Every MBP engagement follows this workflow without exception. Each step has a defined output — so at any point in an engagement, both MBP and the client know exactly where things stand.
The client submits a service request via the website contact form, email at admin@mbptvservices.online, or phone. The inquiry should describe the service needed, the reporting objective, and any relevant timelines. No information is acted on before formal acknowledgement.
Inquiry received and logged. Acknowledgement sent to client within one business day.
MBP reviews the client's objectives, identifies the appropriate service or combination of services, and confirms whether the request falls within standard scope or requires a custom quotation. If clarification is needed, one follow-up is sent before scope preparation begins.
Service recommendation confirmed. Client informed of applicable package or custom scope process.
The full engagement scope is defined in writing — deliverables, reporting frequency, monitoring keywords or topics, delivery format, timeline, and support level. This document becomes the reference point for the entire engagement. No work begins before scope is confirmed in writing by the client.
Written scope document prepared and sent to client for review and confirmation.
A formal proposal is prepared based on the confirmed scope. It outlines the service, deliverables, reporting schedule, pricing, and payment terms. The proposal is sent as a professional document and remains valid for the period stated. Client approval of the proposal triggers invoice preparation.
Formal proposal document sent to client. Awaiting written approval before proceeding.
A formal invoice is issued based on the approved proposal. The invoice includes MBP company details, license number, client reference, service description, amount, and payment terms. Payment is processed before service delivery begins for new engagements. Invoices are maintained permanently in client records.
Invoice issued and filed. Payment confirmed before service delivery commences.
Client provides the monitoring inputs — brand names, keywords, topics, channels, target regions, reporting period dates, and any specific focus areas. For recurring engagements, onboarding details are stored and reused each cycle unless the client requests changes. All onboarding information is held confidentially.
Onboarding record created. Monitoring and reporting parameters confirmed and filed.
Monitoring, analysis, reporting, and advisory activities are performed according to the agreed scope and schedule. Reports are reviewed internally before delivery to ensure they meet the standard described in the scope. Clients are notified if any delay or change to the delivery timeline is anticipated — not informed after the fact.
Report or deliverable prepared and reviewed. Ready for formal delivery.
The completed report or deliverable is sent digitally to the client's confirmed email address. A delivery confirmation is issued alongside the report — recording the date, method, report reference, and engagement details. Both the report and the delivery confirmation are archived permanently in the client file.
Report delivered. Delivery confirmation issued. Full record filed and maintained.
Ready to start an engagement? Send us your service requirement and we will move through steps 1–4 within three business days — scope confirmed and proposal in your inbox.
Start the ProcessTypical Timeline
For a standard engagement, here is a realistic timeline from inquiry to first report. Recurring engagements after the first cycle follow the delivery schedule only — steps 1–6 do not repeat.
You send your service request
Day 1Requirements reviewed, service confirmed
Day 1–2Written scope sent for your approval
Day 2–3Formal proposal and pricing issued
Day 3–4Invoice issued and payment confirmed
Day 4–5Monitoring inputs confirmed
Day 5–6First report delivered on schedule
Per scopeWhat Gets Documented
Every MBP client file contains these six documents as a minimum. They exist for client reference, compliance purposes, merchant account documentation, and audit requirements.
The agreed deliverables, monitoring parameters, reporting frequency, timeline, and support level — confirmed in writing before any work begins. This is the reference document for the entire engagement.
Required before work startsA professional invoice issued for every service engagement — including MBP company name, license number, registered address, client reference, service description, amount, and payment terms.
Issued on every engagementThe actual report, advisory document, or deliverable produced for the engagement — retained in the client archive alongside all other records. Clients may request copies of any previously delivered report.
Archived permanentlyA formal confirmation issued alongside every report — stating the date of delivery, delivery method, report reference, and engagement period. This document serves as proof of service delivery.
Issued with every reportKey client communications — scope approvals, onboarding details, change requests, and follow-up exchanges — are logged and retained as part of the client file throughout the engagement.
Maintained throughoutThe monitoring keywords, brand names, topics, channels, and reporting parameters provided by the client — stored securely and used as the basis for each reporting cycle. Updated only on client request.
Held confidentiallyCompliance & Documentation
Some clients come to MBP not just for the reporting — but because they need a service provider that maintains clean, complete, verifiable records. This applies particularly to clients who need documentation for bank compliance, payment merchant applications, or internal audit requirements.
MBP was built from day one as a formal licensed entity — not a freelance operation that produces informal invoices. Every engagement produces a complete paper trail: scope agreement, formal invoice with license number and registered address, delivery confirmation, and archived report.
This level of documentation is not something MBP added as an afterthought. It is how the business was designed to operate — because the clients it serves often require it.
Official business details for client onboarding, invoicing, and compliance documentation.