You see what we're building. Every week. No surprises at the end.

The two aren't in conflict. Cogworks scopes Catalyst Projects upfront with a fixed deliverable list and a fixed price. Agile is how we organise the internal delivery of that scope: short sprints, regular reviews, early problem detection. If new requirements surface that aren't in the agreed scope, we assess them as a formal change request with a clear cost and timeline implication, agreed before anything moves. You get the predictability of a fixed price and the risk protection of agile delivery.

Cogworks runs weekly written status updates covering what was completed, what's next, and what (if anything) needs a decision. Every sprint ends with a review session where your team sees the working software and gives feedback. A live project tracker is shared from day one so anyone can check the status at any time, without waiting for a meeting. Our team works as an extension of yours: you won't hear "we'll update you at the end of the month."

Scope changes are a normal part of any build. The important thing is how they're handled. At Cogworks, the agreed project scope is the baseline. When a new requirement appears, we assess it: does it fit within the existing scope, or does it represent additional work? If it's additional, we produce a change request with a clear description, cost, and timeline implication before anything moves. Nothing is added quietly. You decide whether to proceed with full visibility of the impact.

Every project has a live risk log, reviewed at each sprint. Risks are rated by likelihood and impact, assigned an owner, and tracked until resolved. Third-party dependencies (integrations, content approvals, design sign-off, legal review) are mapped at the start of the project and tracked explicitly because they're the most common cause of delays in digital builds. When a dependency is at risk, we flag it immediately so your team can act before it becomes a blocker.

Yes. Cogworks regularly takes on delivery management for platforms built by other agencies, particularly where a project has stalled or where an organisation needs stronger governance than their previous partner provided. The typical starting point is a technical review to understand the current state, followed by a structured onboarding into our delivery framework. We've stabilised and re-delivered projects for organisations including Days Out Guide (National Rail) and Prostate Cancer UK.