KB 03: Operational Rules of Engagement

Problem Statement Unclear operational boundaries between a technical partner and a client lead to severe scope creep, unprofitable engagements, and degraded infrastructure performance. When service level agreements are vague, technical support becomes a bottleneck, and the core objective of removing manual waste is compromised by constant administrative meetings.

Commercial Solution All TTS deployments are governed by strict operational hard stops. These limits are non negotiable. They dictate exactly how our logic layers are built, deployed, and supported. By enforcing these rules, we protect the integrity of the logic layer and guarantee that our engineering resources are focused purely on driving commercial results for your business. We refuse to operate at a loss, and we refuse to compromise on technical standards.

Cost Breakdown Our commercial rules dictate our minimum engagement thresholds.

• Profitability Limit: A minimum of £300 per day is required for all contract work. We do not engage in loss leading projects.
• Support Tier Allocations: Capacity is strictly fixed based on your commercial tier. Core receives 2 hours per month. Growth receives 8 hours per month. Enterprise receives 20 hours per month.

Timeline These operational rules are enforced from the moment the commercial contract is signed.

• Day 1: Support allocations are locked in based on the chosen tier.
• Month 1 Onwards: Forensic audits and logic tuning are executed strictly within the allotted hourly limits to prevent scope creep.

Success Metric Guaranteed commercial viability on all accounts. Zero scope creep. 100 percent compliance with support capacity limits, ensuring that the logic layers remain highly tuned without draining engineering resources.

Updated on: 20/02/2026