IT services cover three fundamentally different proposal shapes: fixed-fee projects, retainer agreements, and hybrid time-and-materials arrangements. Each is read by a different buyer. Each has a different page that decides the deal. A fixed-fee project proposal gets scrutinized on scope and milestones. A retainer gets scrutinized on SLA and renewal terms. A T&M proposal gets scrutinized on rate cards and max-hour caps. Proposal tracking tells you which shape you are actually selling, by watching which sections the prospect lingers on.
Below: a representative $72k migration project, a 3-type classification framework that exists on no other IT services page, and a playbook for each shape.
The 3-type IT proposal classification: what each reveals
Every IT services proposal falls into one of three types. Each is read by a different stakeholder first, and the winning follow-up is completely different.
| Proposal type | Who reads first | What tracking reveals |
|---|---|---|
| Fixed-fee project ($15k-$200k) | CTO or technical lead, then CFO on milestones | Architecture dwell = technical confidence. Milestone re-reads = cash-flow objection forming. |
| Retainer agreement ($5-12k/mo) | Ops lead or CIO, then CFO on renewal terms | SLA dwell = response-time concern. Renewal terms re-read = auto-renew clause blocker. |
| Hybrid T&M with cap | CFO first, then technical owner | Rate-card dwell = rate-negotiation forming. Cap clause re-read = scope uncertainty. |
Knowing which type your prospect is reading you as is half the battle. They may have asked for a retainer but read your fixed-fee proposal like a project. Tracking the dwell pattern catches that disconnect.
- Technical objections surface in kickoff
- CFO concerns appear in legal phase
- Scope mismatches discovered in month 2
- Retainer renewal negotiated last minute
- Lost deals are opaque
- Architecture dwell triggers a technical Q&A day 3
- Milestone re-reads trigger proactive restructure
- Proposal-type mismatch flagged by dwell pattern
- Renewal terms re-read triggers early renegotiation
- Every lost deal is a data point
The seven sections that decide an IT services deal
- Discovery recap. Technical champion reads fully.
- Architecture or approach. CTO lives here. Under 90s = trouble.
- Team and rates. Finance + founder.
- Milestones or SLA matrix. The type-defining page.
- Risks and assumptions. Maturity signal.
- Pricing. CFO page. Re-reads = counter forming.
- SOW / MSA. Legal opens. New email = redlines.
Five pain points IT services firms live with
- Three buyer types, one proposal. You pitch technical and commercial at once.
- Scope creep on fixed-fee. Skimmed scope pages become month-2 disputes.
- SLA wording on retainers. Vague response times lose to tiered competitors.
- Rate-card negotiation. T&M deals get renegotiated before kickoff.
- Legal redlines eat weeks. MSA phase is where cycles die.
See which of three proposal types the prospect is actually reading
Afterquoted maps tracked behavior to proposal type. The follow-up is different for each.
Start tracking free →What our cohort shows
IT services firms in our 2026 cohort report the biggest lift comes from catching proposal-type mismatches early. Prospects ask for a retainer but read a fixed-fee. Or vice versa. Tracking flags the mismatch and saves weeks of misaligned follow-up. Across 2,800+ teams our average lift is +38% conversion rate.
Integrations for an IT services stack
- Jira / Linear. Auto-create follow-up tickets on risk or milestone re-reads.
- GitHub. Tracked links to repo plans.
- Slack. Channel pings on high-signal events.
- HubSpot / Pipedrive. Tracked events log as deal activities.