Technical Backlog

Technical backlog support, explained

If you already have a list of changes you want to make, this service turns that backlog into steady progress, with clear estimates and safe releases.

What problems this solves

• A backlog that keeps growing because there is no clear delivery capacity.
• Lots of small issues that add friction for customers and create support load for your team.
• Changes that feel risky to release because there is no staging workflow or release discipline.
• Technical work that gets done without considering conversion impact or measurement risk.

Typical backlog items

This is not a fixed scope list. We use your monthly time budget on the priorities you choose. Typical requests include:

• Bug fixes and stability improvements.
• User experience and user interface improvements, including call to action refinements.
• Template changes and layout adjustments.
• New pages and new templates.
• Custom plugin changes and small feature additions.
• Custom API integrations and third party integrations.
• Tracking and measurement fixes where they affect decision making.

How we run backlog delivery

1. Capture: You raise tasks in Marker.io or your existing tracker. Screenshots and steps to reproduce help us move quickly and reduce back and forth.
2. Triage and estimate: We group tasks, clarify requirements, and give clear estimates. We also flag conversion impact, technical risk, and any dependencies.
3. Build and QA: Work is implemented on staging first. QA includes key flows like product, cart, checkout, and tracking checks where relevant.
4. Release safely: We ship within an agreed release window. For higher risk work, we plan rollback readiness and do tighter post release checks.
5. Report: You get a weekly written update via the StrategyFive dashboard, plus a monthly time report and a clear view of what is next.

Release safety and governance

• Staging first for all meaningful changes.
• Controlled releases within an agreed release window.
• Post release checks for tracking, performance, and checkout flows.
• Monitoring and error logging to reduce incidents and speed up diagnosis.
• WooCommerce best practice development patterns, including using hooks where possible, keeping template overrides minimal, and never modifying core plugin files.
• StrategyFive guarantees the quality of its own work. If something StrategyFive built breaks, StrategyFive fixes it.

How time and billing works

• Development is a monthly retainer that includes StrategyFive Platform and a monthly time budget that can be used for CRO analysis, development, QA, releases, and reporting.
• Billing is monthly in arrears. Time is tracked in 30 minute increments, including meetings, planning, and reporting.
• Unused time can roll into the next month only. You can borrow up to one month of hours forward by agreement.
• On termination, any unused hours are refunded.
• Any time beyond the monthly budget requires explicit written approval and is billed at £75 per hour plus VAT.
• Support is provided during UK business hours as standard, Monday to Friday, 09:00 to 17:30, excluding UK public holidays.

Reporting you can expect

• A live dashboard view of what shipped and performance snapshots, framed as insight rather than a guarantee.
• Weekly burn and delivery update.
• Monthly time report by category, including CRO analysis, build, QA and release, performance and stability, and tracking and measurement.

Is Development the right pathway

If you want StrategyFive to own the roadmap and work through a Performance Gateway with a 12% uplift promise in GA4, that is the CRO Programme. If you want to direct priorities and ship a backlog with clear estimates and safe releases, Development is the right fit.

Next step

If you want to discuss your backlog and choose a time budget, use the Development enquiry form. We will confirm priorities, governance, and a clear monthly cap before work starts.