Direct answer
I would first decide whether the deal justifies trying at all, then compress by cutting scope rather than adding people or demanding overtime, and negotiate with the customer a written, pilot-sized acceptance for day 28 with a dated plan for the rest. A pilot is a limited first release used for real work on a small scale, to prove the value before the full build. Squeezing 12 weeks of work into 4 needs three times the throughput (12 / 4 = 3), which people and overtime do not honestly deliver. What can change is what we promise to have by day 28.
Structured elaboration
Step 1: decide whether to compress. Ask:
- Is the four-week condition firm, or an opening position? Ask Sales to find out what the customer is really trying to do by then (a board demo, a budget cycle, a competing vendor).
- What is the deal worth, and what does the team stop doing for four weeks to make room?
- Is the capability reusable by other customers, or a one-off that becomes a support burden?
If the deal is real, the value is high, and the capability is reusable, I try. If it is a one-off for a modest deal, I decline the date and offer a later one.
Step 2 (worked example): find the slice that fits four weeks. Break the 12 weeks into components, then ask what the customer must see on day 28.
| Component (team-weeks) | Full | 4-week slice | Deferred |
|---|
| Data import | 3 | 2 | 1 |
| Configuration and rules | 3 | 1 | 2 |
| Single sign-on (one login across systems) and permissions | 2 | 0 | 2 |
| Reporting | 2 | 0.5 | 1.5 |
| Audit log and admin tools | 1 | 0 | 1 |
| Hardening (error handling and fixing rough edges) and load testing (checking it copes with realistic usage) | 1 | 0.5 | 0.5 |
| Total | 12 | 4 | 8 |
Every row's slice plus deferred equals its full size, and the columns total 12, 4 and 8.
Why those amounts: the customer's day-28 success is their own data flowing through their own rules, so data import gets 2 of its 3 team-weeks (their real file formats, not every format), configuration gets 1 of 3 (their first two rules, not a general rules engine), and reporting gets 0.5 (the one monthly report they named). Single sign-on and audit log are not needed to see the workflow work, so they get 0. Hardening gets 0.5 so the pilot does not fall over on their first real file.
Step 3: why not just add people or work longer. New engineers take weeks to ramp up and slow the existing team while they do, so a late addition often delays a short project. Overtime for four weeks trades quality for speed, and the defects land in front of the customer we are trying to impress.
Step 4: negotiate with the customer. Ask what must be true on day 28 for them to call this a success; usually it is their own workflow working on their own data, not every feature. Propose the slice as a pilot, and agree in writing:
- Accepted when: their sample files import, their first two rules run, and the monthly report comes out correct, with no critical defects open.
- Explicitly not in the pilot: single sign-on, audit log, full-scale load.
- Their dependencies: sample data and test users by day 5; slip there moves the date.
- The rest: dated, with a firm schedule re-baselined (re-estimated and re-agreed) at the end of week 4 once real use shows the true effort.
What I would say to the customer: "We can have your own data and your first two rules working, with the monthly report, on day 28. Single sign-on and the audit log come in the next phase, and I will give you a firm date for them at the end of week 4, once we have seen your real files. What would you need to see on day 28 to call it a success?"
Step 5: internal discipline. Sales agrees not to promise beyond the written scope. I re-estimate at the end of week 1; if even the slice looks like it will miss, the customer hears in week 2, not week 4.
What would change my call
If the customer's security team will not accept a pilot without single sign-on, the slice grows by 2 weeks and no longer fits, so I would say so and propose a later date or a different pilot setup. If the displaced work is a committed reliability fix, I would decline.
Trade-offs and pitfalls
- A pilot promised as "basically the full thing" is how a four-week deal becomes a twelve-week argument.
- Do not hide the cut scope in the contract; surface it in the first conversation.
- Track what the team stopped doing, and tell its owners.
