Systems Stewardship

It is for clients who have:

• Completed a Breadmaker implementation.
• Existing systems that need regular maintenance and improvement.
• A CRM, automation, onboarding, delivery, or reporting process that is business-critical.
• Ongoing changes to their offers, client journey, team, tools, or workflow.
• A desire for a trusted systems partner without hiring a full-time operations or automation lead.

The exact scope depends on the selected tier, but it may include:

• Monthly system health checks.
• CRM and data-quality review.
• Automation monitoring and error review.
• Minor workflow fixes.
• Dashboard review.
• Lead and client-process optimization.
• Conversion-flow improvements.
• Documentation updates.
• Monthly or quarterly operating review.
• Improvement backlog management.
• AI workflow governance and escalation review.
• Priority support through the agreed channel.

Unless explicitly included, the retainer does not cover:

• Full website redesigns.
• Entirely new CRM implementations.
• New custom applications.
• Major data migration.
• Large new integrations.
• New AI-agent builds.
• Paid advertising management.
• Unlimited design, development, or content work.
• Emergency support outside agreed service hours.
• Third-party platform costs.
• Work outside the monthly capacity allowance.

Material new work is scoped as a mini-project or separate implementation engagement.

A capacity limit protects both parties.

It ensures Breadmaker can give each client reliable attention and prevents the retainer from becoming an undefined collection of urgent requests.

The capacity allowance is designed for maintenance, optimization, small improvements, and strategic support. Major new initiatives are planned and scoped separately.

Breadmaker will recommend one of three paths:

• Use available capacity in the following month.
• Approve additional time at the agreed rate.
• Scope the request as a fixed-fee mini-project.

No material new work begins without agreement on scope, timing, and cost.

Hosting is included only if it is specifically listed in your agreement.

Where Breadmaker manages hosting, self-hosted automation, custom applications, databases, or infrastructure, the agreement should clearly state:

• What is hosted.
• Who owns the account and data.
• Backup arrangements.
• Monitoring coverage.
• Support hours.
• Security-update responsibilities.
• Third-party limitations.
• Offboarding and export process.

Hosting should normally be priced separately from strategic systems stewardship.

Possibly.

Breadmaker may begin with a Stabilisation Sprint or Promise Reliability Diagnostic to understand the existing tools, workflows, documentation, access, data quality, risks, ownership, and support burden.

We do not take responsibility for an inherited system without first assessing it.

Response expectations depend on your plan and agreement.

For example:

Response time means Breadmaker acknowledges and begins triage. It does not necessarily mean every issue will be resolved within that period.

Yes, subject to the minimum term and notice period in your agreement.

A sensible structure is a minimum initial term of [three months], followed by days’ written notice.[insidesales]

On offboarding, Breadmaker should provide the agreed access handover, documentation, and export support. The client remains responsible for third-party subscriptions, data ownership, domain ownership, and platform accounts.