Buying it for a team of 50+

At 5 people, the head of marketing picks a tool with a corporate card. At 50, the same purchase involves IT, security, legal, procurement, and finance, and any of them can stop the deal. The product evaluation that was a 20-minute demo at the small-team stage becomes an 8-week project at this one.

None of this is the vendor's job to manage for you. It's the buyer's job, and it's the part of buying enterprise SaaS that nobody writes about because it isn't glamorous. This guide is the version of the buying process written for the marketing leader who has to actually drive it.

The angle is procurement-aware, not procurement-friendly. The goal is to close the right contract on a tool that survives security review, scales to multi-brand, and doesn't hold your data hostage if you ever leave.

If you're a holding company with 4 brands or an agency with 30 clients, the architecture matters more than the feature list.

Workspaces vs accounts. One workspace per brand is the right model for most multi-brand setups. Separate prompts, separate dashboards, separate reports, shared billing. Avoid tools that force everything into one workspace with brand filters; the data segregation gets messy fast.

RBAC granularity. A marketing manager assigned to Brand A shouldn't see Brand B's data by default. The roles need to enforce that, not the team's discretion. This is especially true for agencies handling competing clients.

Centralised billing. One contract, one invoice, even if 12 brands run on it. Procurement and finance both lose interest fast if they have to track 12 separate invoices.

White-label reporting. If you're an agency, this is non-negotiable. Your clients shouldn't see the vendor's logo on the report; they should see yours.

The line-item price is what vendors lead with. These are the terms that actually determine whether the contract holds up at year three.

Annual with monthly opt-out, not annual upfront. Pay annually for the discount, but with a 30-day notice clause if the vendor materially changes the product or pricing. Most vendors will agree; some won't. The ones who won't are pricing risk into the upfront commitment.

Ramp pricing if you're scaling. If you're adding brands over the year, negotiate ramp pricing instead of paying full year-1 freight for capacity you won't use until month 9.

Renewal price cap. Cap year-two renewal price increases at 5-7%. Vendors who refuse this are telling you they intend to raise prices significantly. Better to know now.

Data export and deletion on termination. Written in the DPA. Full data export within 30 days of termination, written confirmation of deletion after. Without this, the data you collected for 18 months becomes the vendor's asset, not yours.

SLA with credits. Real SLA (99.5% uptime is standard) with actual service credits for breaches. Vendors who only offer "best effort" usually have something to hide about their infrastructure.

The quote shows you the line item. The total cost of ownership over three years looks different.

Implementation: 20-40 hours of marketing time in month 1. Defining the prompt set, configuring the workspace, training the team. Most vendors will help with this; some charge for it; few quantify it in their pricing.

Ongoing operations: 4-8 hours per week. Running the weekly review, refreshing prompts quarterly, acting on the data. This is the cost that doesn't appear on the invoice and usually isn't planned for.

Renewal escalators. Without a renewal price cap, year 3 can be 1.5x year 1. Run the model both ways before you sign.

Sunk-cost migration risk. If you ever want to leave, the cost isn't the new tool; it's recreating 18 months of prompt sets, custom reports, and team workflows on the new platform. Optimise for portability now, not later.

Working backwards from a target signing date.

Weeks 1-2: Marketing builds the shortlist (3 vendors max), runs demos, picks the lead candidate. Don't waste security and procurement's time on more than three.

Weeks 3-4: Security review. SOC 2 report, vendor questionnaire, identity integration test. Run this in parallel with legal starting on the DPA.

Weeks 5-6: Legal redlines on the DPA and MSA. Procurement starts the pricing negotiation in parallel. This is where the slowest stakeholder dictates the timeline.

Weeks 7-8: Final contract execution, paid pilot start. The pilot runs against the production product, not a sandbox.

Anything faster than this usually means a step got skipped (often security or DPA) and will get rediscovered painfully at renewal. Anything slower usually means one of the buyers wasn't given the right materials at the right time.