Buying a website in Chicago: how to scope it, brief it, and read the proposals

Most Chicago businesses buy a website badly, and it is rarely their fault. They ask three shops for a quote, get back three documents that describe different projects at wildly different prices, and pick based on gut feel. The fix is not finding a better agency. It is scoping the work precisely enough that the proposals become comparable.

Here is how, including the parts specific to Chicago and Illinois.

Scope before you shop

Four decisions set the price of almost any web project. Make them yourself, in writing, before you contact anyone. Skip this and the agency makes them for you inside its own proposal, and you end up comparing assumptions rather than quotes.

1. Who reads the site, and in which language

Spanish is the largest non-English language in the city by a wide margin, concentrated in neighbourhoods like Pilsen, Little Village, Gage Park and Brighton Park. Polish is the second most common language spoken at home in Chicago, clustered on the Northwest Side around Jefferson Park, Norwood Park, Avondale and Dunning. If you are a home services company, a clinic, a law firm or a contractor working those areas, a Spanish version of your site is a revenue decision, not a diversity gesture.

Decide this at scoping time, because it changes everything downstream. A second language means a URL structure that supports it, hreflang tags, a CMS that holds parallel content, a translator on the budget, and a plan for who keeps the Spanish pages in step when the English ones change. Bolting it on later costs more.

2. What data the site collects

Illinois has no comprehensive consumer privacy statute in the mould of California's, but it has narrow laws with real teeth. The Biometric Information Privacy Act (740 ILCS 14) covers five things: fingerprints, voiceprints, retina or iris scans, hand geometry and face geometry. It carries a private right of action, which is why it generates so much litigation. The 2024 amendment (Public Act 103-0769) ended per-scan damage accrual, but it did not remove the exposure.

That matters if your site does anything clever. Face matching in a customer portal, voice authentication on a support line, a gym or salon booking flow tied to fingerprint check-in. Each needs explicit written consent and a published retention schedule. Raise it up front so it is designed in, not discovered in week nine.

Two more Illinois rules worth naming. The Personal Information Protection Act (815 ILCS 530) sets breach notification duties, so whoever holds your form submissions needs a documented process. And since 1 January 2026, HB 3773's amendment to the Illinois Human Rights Act requires employers to notify candidates when AI is used in hiring, and bars ZIP codes as a proxy for protected classes. If your careers page runs an AI screener, that notice belongs in the build scope.

3. Whether it takes money, and how

Chicago's tax position is unusual enough to change a technical brief. The combined sales tax rate in the city sits at 10.25 percent, and the RTA share in Cook County rises after June 2026, taking the combined rate to 10.50 percent. If you sell physical goods online, your checkout needs tax handled by an engine that tracks rates at ZIP level rather than a hardcoded number someone typed in once.

If you sell software or anything cloud delivered, the Personal Property Lease Transaction Tax is the one to raise early. Chicago's 2026 Revenue Ordinance took it from 11 percent to 15 percent effective 1 January 2026, and it reaches SaaS and cloud services used by Chicago customers. That affects billing logic, invoice presentation and how your pricing page states what a customer actually pays. It is also the sort of thing a generalist agency will not ask about, and their silence tells you something.

On payment methods, be realistic about your buyers. Consumer checkout means cards, Apple Pay and Google Pay. B2B in Chicago's logistics, manufacturing and construction sectors still runs on ACH, net terms and paper checks. A card-only checkout aimed at a freight brokerage solves the wrong problem.

4. Who updates it after launch

This answer determines the platform choice and half the ongoing cost. If your marketing coordinator needs to publish a service page without filing a ticket, say so. If nothing will change for two years, say that too and stop paying for flexibility you will never use.

Accessibility is a Chicago-specific risk, not a nice-to-have

The Northern District of Illinois has become one of the busiest venues in the country for website accessibility claims under Title III of the Americans with Disabilities Act, partly because the court reads the ADA to cover online-only businesses. Illinois moved into the top three states for these filings in 2025.

So your proposal should name a standard, WCAG 2.2 Level AA, and describe how it gets tested. Ask whether testing includes keyboard-only navigation and a screen reader, or just an automated scanner. Scanners catch a minority of real issues, and an agency promising compliance from a plugin alone is selling a false sense of safety.

Separately, if you sell to the State of Illinois or any body spending state funds, the Illinois Information Technology Accessibility Act applies to that work. Say so in the brief. It changes the acceptance criteria.

What a good proposal looks like

With a written scope, proposals become easier to judge. Look for these.

• A page inventory, not a page count. Five unique templates and forty pages is a different project from forty unique layouts. The proposal should say which.
• Named responsibility for copy. If it does not say who writes the words, nobody does, and the project stalls in month two.
• A stated performance target. Core Web Vitals thresholds, measured on real visitor data after launch, not a lab score from the developer's machine.
• Integration specifics. Not "CRM integration" but which CRM, which fields, and what happens when the sync fails.
• Ownership terms. You should own the repository, the domain, the analytics property and the CMS account. Get that written down.
• A change process. How out-of-scope requests get priced, so the first one does not turn into an argument.

And the warning signs, which are consistent across every market we work in.

• A fixed price with no scope attached to it. That number is a negotiating position, not an estimate.
• SEO promised as rankings rather than as technical work you can inspect.
• A portfolio with no live URLs. Screenshots prove nothing about performance or accessibility.
• No mention of what happens after launch, or a maintenance retainer with no defined deliverable.

Vetting: three checks worth doing yourself

1. 01Open two sites from their portfolio on your phone, on cellular, not office wifi. Ride the Red Line and load them underground if you want the honest version. Chicago buyers do a lot of browsing between the Loop and wherever they live.
2. 02Run one of their live client sites through a screen reader for two minutes. You will learn more in that time than in an hour-long call.
3. 03Call one reference and ask a single question: what went wrong, and how did they handle it. Every project has one. The answer tells you how the next one will go.

The time zone question, asked honestly

FuturByte is a Dubai studio. We have no Chicago office and no staff there, and if a vendor tells you otherwise you should check it. Dubai runs nine hours ahead of Central Daylight Time and ten hours ahead in winter, which means our afternoon is your morning. In practice that gives a reliable daily overlap from roughly 8am to 11am Chicago time for calls, and work landing in your inbox before you start. It also means a question asked at 4pm Chicago time waits until the next day. That is a real trade-off, and you should price it against a local shop rather than have it glossed over.

If a proposal does not mention Illinois accessibility exposure, language coverage, or how tax is handled at checkout, the agency has not read your market. That is a more useful signal than their portfolio.

Write the scope, send the same document to three firms, and compare what comes back. If you want a second opinion on a proposal you have already received, including one that is not ours, send it over and we will tell you what we would push back on.