There is a familiar shape to traditional consulting engagements for small and mid-sized businesses. A partner from the firm turns up, takes a long lunch with the owner, and proposes a four-to-six month project. The fee scales with seniority of the team you'll meet once and the juniors you'll meet every day. At month three, the intermediate readout reveals that the findings are roughly what anyone who has worked inside the business for a year could have told you in a paragraph — dressed up in a framework, with quadrants.
This is not always what happens. But it is often enough what happens that most owner-operators have a story about it. The question is why the industry is shaped this way, and whether the shape is actually serving the business being advised.
Why engagements get longer than the work requires
Three reasons, none of them sinister.
First, the fee model. Large consulting firms are optimised to bill hours against a rate card. The rate card works because clients pay for weight: a project with five people on it for four months reads as serious. A project with one person on it for a week reads as unserious, even if the output is tighter. The market has been trained to associate insight with duration, and the pricing model makes duration the profitable lever.
Second, scope insurance. A four-month engagement buys time to explore. The first two months are genuinely useful — reading the documents, meeting the team, understanding the business — and the last two months are insurance against having missed something. The insurance has value. The question is whether the value of the insurance is greater than the cost of paying for it, every time, on every engagement.
Third, the relationship model. Longer engagements build relationships, which build follow-on revenue. This is legitimate and not necessarily against the client's interest, but it is not the client's interest either. A client does not benefit from an engagement lasting a week longer than the analytical work requires. A firm does. That asymmetry gets smuggled into the default project duration.
What a short engagement forces
A seven-day engagement with a fixed deliverable is not a smaller version of a longer engagement. It is a different shape. Several things change when you remove the ability to scope-creep.
The intake conversation becomes real. When you have seven days, you cannot afford to discover in week three that you've been asked to solve the wrong problem. The intake call has to be good. Both parties have to be honest about what they want. If the real question is "is my business going to survive the next year", that needs to be said at day zero, not implied at week six.
The report has to be readable. Nobody pays $800 for something they can't read in an hour. The document is compressed. The recommendations are prioritised ruthlessly because there isn't room to list ten and let the client pick. The consultant has to have a view, and has to defend it on the page, rather than presenting alternatives and letting the client do the work of choosing.
The answer can be "don't do anything radical". The longer a consultant is on the ground, the harder it becomes to submit a report that says the business is largely fine and needs to change three small things. The investment of time is self-justifying. A seven-day engagement has no self-justification problem. If the honest answer is to tighten three procedures, that's what the report says, and the fee is the same.
The client keeps the work. Short engagements produce written artefacts that the business owns and uses. Longer engagements produce relationships that the business is dependent on. Ownership matters. The report on the owner's desk is a document she can hand to her plant manager and her finance lead the next morning. A consultant on a retainer is someone she has to call.
Where shorter engagements do not work
This is not a universal argument. Some problems cannot be resolved by a written report and a delivery call. If the work is genuinely a transformation — replacing a core system, rebuilding the finance function from scratch, taking a company through a merger — a short engagement is the wrong vehicle. Those projects need months, multiple people, and a budget that reflects it.
The seven-day review is not the right tool for every problem. It is the right tool for the specific problem of an owner-operator who needs a clear, defensible, actionable read on how the business runs — written by someone who has operated a business in that shape, and is not trying to sell a bigger engagement on the back of it.
The honest contract
Productising a consulting offer is sometimes framed as a commoditisation move — "we sell assessments like groceries". That framing misses the point. The productisation is a contract between the consultant and the client that neither side is going to pretend this is something it isn't. The client is not signing up for a relationship. The consultant is not padding the week. Both parties know exactly what is being delivered, by when, and for how much.
Honest, compact work has been undervalued by the consulting industry for a long time, because it does not grow a firm. It suits a practice run by an operator, not a firm run by partners. That is what 720 Degrees is.
If you want to see what the written output looks like, there is a composite sample at /assessment/sample-assessment. If you want to have the intake conversation, the form is on the assessment page. That is the whole offer. Nothing else is being sold.
By Terence Grenfell, founder, 720 Degrees. Published April 2026.