What your developer said, in English.
104 terms you will hear on sales calls, in proposals and in contracts, each with a plain definition and the line other glossaries leave out: what it means for your money and your risk.
Glossary
Platforms and the build
The words developers use to describe what your site is made of, and what each one costs you later.
CMS (Content Management System)
The software you log into to edit pages, posts and products without touching code. WordPress is the best-known example.
Why it matters: Who can operate the CMS decides your running costs: a familiar system means ten minutes of training for staff; an exotic one means calling the developer for every comma.
Theme / template
A pre-built design system your site wears. Multiple pages usually derive from a handful of templates.
Why it matters: Ten pages from three templates is a fraction of the cost of ten bespoke designs, usually the better deal. Ask any quote how many unique templates it includes.
Plugin
An add-on that gives a platform extra features, forms, SEO tools, checkout add-ons, and so on.
Why it matters: Every plugin is a dependency: it must be updated forever and each one is a possible security hole. More plugins, more maintenance. Unused plugins should be deleted, not deactivated.
Custom post type
In WordPress, a purpose-built content bucket, "case studies", "properties", "team members", with its own fields and layout.
Why it matters: The difference between a site your staff can maintain and one where every new listing is a developer call. Cheap to plan in, expensive to retrofit.
Headless CMS
A content system that stores your content and serves it to any front end via an API, decoupling editing from presentation.
Why it matters: More flexibility and speed for the right project, and a second system to run forever. Pay for it when the front end genuinely needs it, not for architecture fashion.
Staging environment
A private copy of your site where changes are made and tested before going live.
Why it matters: If a developer cannot show you a staging site, you are the QA department. Insist on one and keep it after launch.
Repository (Git)
The versioned record of your site's code, who changed what, when, with the ability to roll back.
Why it matters: Repo access from day one is the single strongest predictor of a clean exit. A developer who resists it is telling you how the relationship ends.
Deployment
The act of pushing code changes from the repository to the live site.
Why it matters: A documented, repeatable deploy process means changes are boring. Improvised deploys means launch nights are exciting, and not in a good way.
Handover
The documented transfer of everything: credentials, architecture notes, how-to-run-it instructions.
Why it matters: A website nobody else can operate is not delivered. Make the handover pack a contractual deliverable, not a favour.
Page builder
A drag-and-drop tool for assembling pages visually without writing code, popular on WordPress.
Why it matters: It gives your staff the power to edit pages themselves, which is real value. But it is also a plugin that must be updated forever and can add weight to every page, so count its ongoing update and speed cost into the decision.
Child theme
A layer of customisations on top of the main theme, kept separate so updates do not break them.
Why it matters: Code pasted straight into a theme is silently erased on the next update. A child theme is the whole difference between a clean upgrade and discovering your customisations vanished.
API
The standard method two systems use to exchange data, your site talking to your CRM, payment processor or mailing list.
Why it matters: APIs decide which integrations are possible and how much they cost to build and maintain. Every integration is a permanent dependency, not a one-time checkbox.
Webhook
An automatic notification one system sends another when something happens, a payment, a form submission.
Why it matters: It is how your forms, payments and inboxes stay in sync without manual copying. Missing webhooks fail silently, which is exactly why they need explicit testing before launch.
Glossary
Money and scope
The contract vocabulary. Every one of these words is a place budgets leak.
Scope
The written list of what the project includes, pages, features, integrations, and just as importantly, what it does not.
Why it matters: Undocumented scope is the number one cause of blown budgets. If it is not written down, it does not exist, no matter what was said on a call.
Scope creep
The quiet accumulation of "small" additions after the scope is agreed.
Why it matters: Creep is not free, it is billed somewhere: in change orders, in resentment, or in corners cut later. The fix is a written change mechanism, priced before work.
Change order
A written, priced approval for work outside the agreed scope, signed before that work starts.
Why it matters: Change orders feel bureaucratic until the alternative arrives: a final invoice full of surprises. Good developers volunteer them.
Milestone
A defined checkpoint where specific deliverables are verified and a payment is due.
Why it matters: Milestones make progress verifiable and give you a clean exit ramp: part ways at any gate, pay for what is verified, keep what is built.
Deposit
An upfront payment before work begins, typically 10–50% of the project.
Why it matters: Deposits are normal; full payment upfront is not. Anything above 50% before delivery should make you ask hard questions.
Fixed price vs time & materials
Fixed price pins the total to a written scope; time & materials bills actual hours, flexing as the work evolves.
Why it matters: Fixed price shifts risk to the developer (so the scope must be airtight); T&M shifts it to you (so the reporting must be honest). Neither is wrong, ambiguity between them is.
Discovery phase
A short, paid engagement to turn "we need a website" into a written, quotable specification.
Why it matters: On fuzzy projects, paying for discovery is how you get comparable quotes instead of guesses. It is not padding; it is the quote being manufactured.
Retainer
A recurring monthly fee for ongoing work, maintenance, updates, small improvements.
Why it matters: Most market retainers sit between $500 and $3,000/month. A retainer quote that cannot say what it covers, its response times, and how it cancels is a subscription, not a service.
Quote vs estimate
A quote is a fixed, written price for agreed work; an estimate is a looser guess at what it might cost.
Why it matters: The word in the document decides what you can hold a developer to. A quote fixes the number; an estimate reads as a floor that spending can only climb from.
Acceptance criteria
The written tests a deliverable must pass before it counts as done, this page loads, this form submits, this checkout completes.
Why it matters: Without them, "done" is whatever the developer says it is. Passing your acceptance checks is the only definition of finished that protects the money you have already paid.
Glossary
Speed and search
The metrics Google actually measures, and the words agencies use to sound like they do.
Core Web Vitals
Google's three user-experience metrics: loading (LCP), interactivity (INP), and visual stability (CLS).
Why it matters: They are a ranking input and a conversion input, slow sites bleed both. A good developer quotes targets ("LCP under 2.5s") instead of saying "we optimise".
CLS (Cumulative Layout Shift)
How much the page jumps around while loading, the banner that slides down as you tap a button.
Why it matters: Layout shift directly causes mis-clicks and lost form submissions. It is usually an image-sizing discipline, cheap at build time, annoying later.
CDN (Content Delivery Network)
A global network of servers that serves your site's files from near the visitor instead of one distant data center.
Why it matters: A CDN is often the cheapest meaningful speed upgrade available, sometimes free. A proposal without one for an international audience has a hole.
Caching
Storing ready-made copies of pages and assets so they do not get rebuilt for every visitor.
Why it matters: Caching done well is invisible speed. Caching done badly is the reason your client "still sees the old site", it needs a documented purge process.
Meta tags
The page title and description shown in search results and social shares.
Why it matters: They are your ad copy in the search results. Unique per page is table stakes; a generator that spits out duplicates is a quiet traffic leak.
Structured data (schema)
Machine-readable labels on pages that tell search engines what things are, a service, a price, an FAQ, a business.
Why it matters: This is how pages earn rich results instead of plain blue links. Cheap to include at build; routinely forgotten.
Sitemap.xml
A file listing every URL you want search engines to know about.
Why it matters: Should be auto-generated and submitted at launch. Its absence on a new site is a two-week ranking delay for no reason.
Robots.txt
A file telling crawlers which areas of the site they may fetch.
Why it matters: A misconfigured robots.txt can quietly deindex an entire site. It is five lines long and worth reading once.
301 redirect
A permanent signpost that a URL has moved, passing visitors and search equity to the new address.
Why it matters: Redirects are the whole ballgame in migrations. Every old URL needs a mapped destination, or the rankings die at the 404s.
Alt text
The written description of an image, read by screen readers and shown when images fail.
Why it matters: Accessibility obligation first, cheap SEO second. Missing alt text fails real users and audits alike.
INP (Interaction to Next Paint)
How quickly the page responds to a tap or click, the metric that replaced FID for scoring interactivity.
Why it matters: A site that feels laggy to click loses form fills and checkouts even when it looks fast. It is a ranking input and a promise a developer can actually quote instead of hand-wave.
Lazy loading
Deferring off-screen images, videos and widgets so they load only when a visitor scrolls near them.
Why it matters: It is one of the cheapest speed wins there is, it trims page weight and lifts mobile performance without touching design. A build that skips it is leaving free performance on the table.
Glossary
Security and operations
The boring words that decide whether the site survives contact with the internet.
SSL / TLS certificate
The certificate that makes your site load over HTTPS and encrypts traffic.
Why it matters: Non-negotiable: browsers flag HTTP sites as unsafe, and forms without encryption are a liability. It is free (Let's Encrypt); nobody should charge you monthly for it.
Backup
A restorable copy of the site's files and database, stored away from the server.
Why it matters: A backup on the same server is a coincidence, not a plan. Ask where backups live, how old the newest is, and, the killer question, when a restore was last tested.
Tested restore
Actually rebuilding the site from a backup, on a staging environment, proving it works.
Why it matters: An untested backup is a hope. Restore drills are the difference between a bad hour and a dead business.
Uptime monitoring
An external service that checks the site is up and alerts a human when it is not.
Why it matters: Customers find out about outages before owners do, otherwise. Monitoring is a few dollars a month and non-optional for a revenue site.
Two-factor authentication (2FA)
A second proof of identity beyond the password, a code, an app, a key.
Why it matters: Passwords leak constantly. 2FA on hosting, CMS admin and domain registrar stops the majority of account-takeover site defacements.
Access credentials
The logins that control everything: domain registrar, hosting, CMS admin, email, analytics.
Why it matters: All of them should be in your name from day one, held by you, lent to the developer. The reverse arrangement is how businesses lose their own websites.
DNS
The internet's address book that points your domain to your hosting and email.
Why it matters: DNS is where "we lost the domain" stories start. Know your registrar, keep the account in your name, and lock transfers.
Maintenance plan
The recurring arrangement for updates, backups, monitoring and small fixes after launch.
Why it matters: A site is a subscription with occasional capital expenses, not a purchase. The plan should state what it covers, response times, and how it cancels, in writing, before launch.
Web application firewall (WAF)
A filter that sits in front of the site and blocks common attack traffic before it reaches your application.
Why it matters: Most attacks are automated and aim at the same known holes. A WAF is cheap insurance against the spam-flood scenarios, but it still needs monitoring, a firewall nobody watches stops stopping things.
Auto-updates
Automatic patching of the CMS, plugins and themes as new versions are released.
Why it matters: Unpatched software is how sites get compromised. Auto-updates close that gap but carry a small risk that an update breaks something, which is exactly why they belong behind a tested staging environment.
Glossary
Ecommerce
Store vocabulary, where every term has a fees-and-failure story attached.
Payment gateway
The service that actually processes card payments at checkout, the processor, not the cart.
Why it matters: Gateway fees (typically ~2–3% plus a fixed amount) are a permanent tax on revenue. Which gateway, at what fees, with what alternatives, is a launch decision, not a detail.
Checkout flow
The steps between "buy" and "paid": cart, address, shipping, payment, confirmation.
Why it matters: Most cart abandonment happens here. Every extra field and surprise cost is a measurable leak, test it yourself, with a real card, before launch.
Abandoned cart email
The automatic follow-up sent to shoppers who left at checkout.
Why it matters: One of the highest-ROI emails in ecommerce and cheap to set up, if it is scoped into the build instead of discovered missing after the first Christmas.
Tax and shipping zones
Rules that decide what each customer is charged based on where they live.
Why it matters: Boring, fiddly, and legally load-bearing. This is the line item where store builds quietly overrun, it belongs in the quote, tested with real scenarios.
Product data migration
Moving the catalog, products, variants, images, descriptions, categories, to the new platform.
Why it matters: Frequently the single largest hidden cost in a store project. Get an explicit answer: who exports, who cleans, who enters, priced how.
PCI compliance / card handling
The rules about how card details are collected, stored and transmitted when payments are processed.
Why it matters: Storing card data on your own system is a heavy obligation; pushing payments straight to a hosted gateway keeps that liability with the processor. Where the card data lives is a legal decision, not a technical detail.
Inventory management
How stock levels are tracked across products, variants and sales channels as things sell.
Why it matters: Overselling and stock confusion cost real money and real customers. Confirm whether the platform tracks stock for you or whether you are maintaining a spreadsheet and hoping.
Glossary
Money and contracts
The clauses that decide who owes what to whom, and who owns what, once the work is done, or stops halfway.
Retention of title
The clause that ownership of the work stays with the developer until the final payment clears.
Why it matters: It answers who actually owns what you have paid for so far. A half-paid project you can finish elsewhere is leverage; one you cannot is a hostage.
Service level agreement (SLA)
Written commitments for things like response times, fix windows and uptime, usually in the support or maintenance contract.
Why it matters: All the talk about "we respond fast" only becomes enforceable when it is written as a number in a signed document. A contract without an SLA is a promise with no floor.
Kill fee
The agreed amount you pay to cancel the project partway, covering work done so far and nothing more.
Why it matters: A stated kill fee means you can walk away knowing the exact price. Without one, the figure is invented at the moment you are most exposed.
IP assignment
The clause that transfers ownership of the code, design and content to you on completion.
Why it matters: By default the developer often owns the work and merely licenses it to you. Assignment is what lets you resell the site or move it elsewhere, without it, your exit is someone else's property.
Source code escrow
Your site's code held by a neutral third party and released only if the developer stops maintaining it.
Why it matters: It is insurance against the developer-disappears scenario. A site nobody can touch is a depreciating asset, and escrow is the cheap answer to that specific fear.
Warranty / defect liability period
The window after launch, typically 30 to 90 days, during which fixing defects is free.
Why it matters: Launch almost always surfaces a few real problems. This window decides whether those fixes are part of the deal or billed a second time, so define it in writing and test hard inside it.
Payment terms
When invoices are due, commonly net-14 or net-30 days after issue.
Why it matters: Agreed terms keep cash flowing without a dispute over timing, on both sides. Written terms are the difference between a mild disagreement and a project that stalls over money.
Late payment clause
The agreed consequence of paying an invoice past its due date, typically an interest charge or paused work.
Why it matters: It protects the developer from being an unpaid bank, and it protects you too: defined terms mean no one can quietly hold work hostage over an unnoticed invoice.
Cancellation clause
The written rules for how either side can end the agreement, notice required, what is paid, what is handed over.
Why it matters: Exiting is a contractual right, not a favour. A clean cancellation clause means you leave with your code, your data and your settled bill instead of negotiating for them at a bad moment.
Glossary
Domains, hosting and email
The plumbing behind your web address, where lock-in and silent failures actually live.
Registrar
The company you buy your domain name from and renew it with.
Why it matters: The registrar account is where domain-lost stories start. Keep it in your own name and email, or you are a guest in your own web address.
Nameserver
A server that holds a domain's DNS records and answers where the domain points.
Why it matters: Nameserver changes are how one host takes over your site and email, and how they can hold it hostage when you leave. Know which nameservers are set and who controls them.
MX record
The DNS record that tells the internet where email for your domain is delivered.
Why it matters: A wrongly set MX silently kills incoming mail, and customers notice before you do. It is a few lines long and worth verifying every time hosting moves.
Domain transfer
Moving a domain between registrars, which needs an authorisation code and an unlocked account.
Why it matters: The unlock requirement protects you from theft, but it also means a domain in a developer's locked account cannot be moved by you. Keep the registrar account yours so leaving is your decision.
Shared vs managed hosting
Shared hosting runs your site on a server packed with other sites and is cheap. Managed hosting has a vendor handling updates, security and speed for you.
Why it matters: Cheap shared hosting suits a small site and wilts under real traffic; managed costs more but removes the sysadmin work. The trade is price now against downtime and headaches later.
Business email
Email at your own domain, you@yourdomain.com, rather than a free consumer address.
Why it matters: It is cheap, lasting credibility, and an address at your own domain is one you keep when you change hosts or providers. Cheap now, and it survives any platform switch.
Email deliverability (SPF/DKIM)
Technical records that prove your domain is allowed to send its own mail, so it reaches inboxes instead of spam.
Why it matters: A store or contact form that cannot send mail is a silent failure your customers feel first. These records are usually the difference between the inbox and the spam folder, and they cost nothing.
Domain renewal / auto-renew
The setting that keeps your domain registration paid and active, automatically.
Why it matters: An expired domain can be parked by a squatter or sold, taking your traffic and reputation with it. Auto-renew on a working card is a five-minute setting that prevents a real catastrophe.
Domain privacy (WHOIS)
A service that hides your personal contact details from the public domain registry records.
Why it matters: Without it your name, address and phone are published for anyone to scrape. It is a few dollars a year and quietly worth it.
Subdomain
A separate address hanging off your domain, like shop.yourdomain.com, often used for stores, blogs or separate apps.
Why it matters: Subdomains let you run distinct systems on one domain, but search engines treat each as its own site. Useful structure, just decide it deliberately rather than inheriting it by accident.
DNS propagation
The delay, minutes to hours, before a DNS change is visible across the whole internet.
Why it matters: It explains "it is fixed but still not working" right after a change. Knowing it is normal stops you paying to debug a problem that has already been solved.
Glossary
Search and growth
The measurement and structure that decides whether the site earns its keep, and whether the developer did the job.
Google Search Console
A free Google tool showing how its crawler sees your site, indexed pages, errors, and which queries bring traffic.
Why it matters: It is the instrument panel for whether your site is actually being found. Verify it into your own account at launch; a site you cannot inspect is a site you cannot fix.
Google Analytics (GA4)
The free analytics service that counts visitors, what they do, and where they come from.
Why it matters: Traffic without measurement is a guess, and every later decision is judged against the baseline it sets. Set up at launch, it turns a website into something you can hold accountable.
Conversion tracking
Measuring a specific action, a purchase, a form fill, a phone call, rather than just counting visits.
Why it matters: This is how you know which pages actually earn money instead of merely attracting traffic. A site without it is flying blind on its own performance.
404 page
The page shown when a URL no longer exists.
Why it matters: A good 404 apologises and points visitors somewhere useful; a bare error dead-ends paying customers. Cheap to build well, and it quietly preserves trust during any redesign.
Noindex
A tag telling search engines not to list a page, used for thank-you pages, admin areas and thin content.
Why it matters: Keeping junk and duplicate pages out of the index protects attention for your real pages. It is the 'keep out' sign too many sites forget, and forgetting it dilutes what matters.
Heading structure (H1–H3)
The hierarchy of page headings that both readers and search engines use to understand a page's structure.
Why it matters: It is readability for humans and context for search engines, and it is nearly free to get right at build time and tedious after. Every page should carry exactly one H1.
Internal linking
Links between pages on your own site that guide visitors and search engines through related content.
Why it matters: These links spread attention across your site and keep people moving instead of bouncing. They cost nothing but thought, and their absence signals a thrown-together build.
Mobile-first indexing
Google's practice of treating the mobile version of your site as the primary one for ranking.
Why it matters: If the mobile version is broken or stripped down, that is the version the search engines judge. Test what a phone visitor actually gets, that is the page ranking sees.
Glossary
Search and growth, the invoice-level words
The search vocabulary that decides whether the site earns traffic, and what the invoices for it should look like.
Field data vs lab data
Field data is measured on real visitors over 28 days; lab data is a simulated single run in a testing tool.
Why it matters: Vendors screenshot green lab scores because they are instant and flattering. Your rankings use field data. Contracts should name which one the deliverable moves.
Render-blocking resources
CSS and JavaScript the browser must download and process before it can paint anything.
Why it matters: Every blocking script is a queue your visitors stand in with a blank screen. Shrinking that queue is free performance, no new hosting plan required.
Rich result
A search listing with extras, star ratings, prices, FAQs, enabled by valid structured data.
Why it matters: No vendor can guarantee rich results; Google decides display. What can be delivered is eligibility: correct, complete markup on pages that qualify.
Crawl budget
The number of pages a search engine will actually crawl on your site in a given period.
Why it matters: On large catalogs, wasted crawling on facet URLs and duplicates is budget stolen from your real pages. Architecture fixes it, content never gets the chance to.
Faceted navigation
Filter menus (by size, colour, price) that generate a new URL for every combination.
Why it matters: The classic ecommerce trap: a 500-product store can generate half a million filter URLs. Whether your platform handles them correctly is an architecture question worth asking before the build.
Indexing
The search engine actually including your page in its results database, a page can be crawled and still not indexed.
Why it matters: "Discovered, not indexed" in Search Console is the quiet killer: the page exists, Google saw it, and decided not to keep it. Thin, duplicate or doorway pages get exactly that treatment.
Doorway pages
Many near-identical pages built to catch slightly different searches rather than to serve people.
Why it matters: Google explicitly demotes them, the playbook that sold you 300 near-identical landing pages is a liability, not an asset. Depth beats count, every time.
Google Business Profile (GBP)
The free listing that controls how you appear in local search and maps.
Why it matters: For local work it outranks your website: categories, service areas and review flow decide the map pack. It is setup plus minutes a month, not a permanent retainer.
NAP consistency
Name, address and phone matching exactly, site, profile, and every directory.
Why it matters: Mismatched details split your local identity and trust. Fixing it once is cheap; paying monthly to not fix it is the local-SEO retainer business model.
Log file analysis
Reading your server logs to see what search crawlers actually request, page by page.
Why it matters: The honest source for crawl-budget answers, what Googlebot wastes on and never reaches. Enterprise audits include it; small sites rarely need it.
Organic CTR
The share of people who see your listing in results and click it.
Why it matters: Ranking without clicks is a tree falling unheard: titles and descriptions decide CTR, and they are the cheapest optimisation in search, copy, not code.
AEO (Answer Engine Optimisation)
Being cited as the source when AI answer engines (ChatGPT, Perplexity, AI Overviews) respond to a question.
Why it matters: A growing share of buyers never see a results page. The work overlaps SEO fundamentals, structure, markup, genuine expertise, which is why it should not be a separate line item on every invoice.
hreflang
Markup that tells search engines which language or regional version of a page to show which audience.
Why it matters: Multi-market sites without it serve the wrong flag to the right customer. It is fiddly, unforgiving of typos, and priced accordingly, ask whether you actually serve multiple locales first.
SERP
The search engine results page, the list (and ads, and maps, and AI answers) a searcher sees.
Why it matters: Where your listing competes for clicks against everything else stacked above it. Ranking third in a SERP with ads and an AI summary can mean fewer visits than ranking first did two years ago.
Map pack
The block of three local businesses with pins that appears in local search results.
Why it matters: For local intent it outranks every website, including yours. What decides it (proximity, profile completeness, reviews) is mostly not your website at all, which is why "website SEO" alone does not move it.
SEO retainer
A recurring monthly fee for ongoing search work, content, links, technical maintenance, reporting.
Why it matters: Honest when the work genuinely recurs; a subscription on a solved problem when it does not. The test: ask what specifically ships this month that last month did not.
Front-end development
The code that renders what users see and touch in the browser, layout, interactions, forms, accessibility, performance on the device.
Why it matters: Front-end quality is what visitors experience directly; it is also where most DIY sites leak speed and accessibility without anyone noticing until rankings or sales slip.
Back-end development
The server side: databases, business logic, authentication, integrations and everything that processes and stores what the front end shows.
Why it matters: Back-end quality decides whether your data is safe, your checkout is reliable and your site can grow, none of which is visible until the day it fails.
Full-stack developer
A developer who works across both front-end and back-end. Efficient for common projects; "full-stack" is also the most inflated title in hiring, so depth-probe both ends.
Why it matters: Hiring full-stack for a project whose risk lives entirely on one side is paying generalist rates and hoping on the specialist half. The decision rule: hire where the risk lives.
Responsive web development
Building pages that adapt correctly to every screen size, phones, tablets, laptops, wide monitors, without breaking layout or usability.
Why it matters: Most of your traffic is on phones. Responsive is not a feature; it is the baseline, and its absence quietly taxes every visitor before they read a word.
Bootstrap
A widely used front-end CSS framework that ships pre-built components and a grid system, fast to assemble, easy to recognize.
Why it matters: Bootstrap sites ship fast and can look fine, but the default look and the unused-CSS weight are real tradeoffs. What matters is whether the stack was chosen for the project, not by habit.
Web development framework
A structured toolkit (Next.js, Laravel, Django, Rails) that standardizes how an application is built, routing, data, security patterns, so developers stop rebuilding plumbing.
Why it matters: The framework choice shapes your maintenance costs and hiring pool for years. A mainstream framework is a safer bet than a fashionable one, because you can always hire for it.
Gemini API
Google's API for its Gemini AI models, the pay-per-use route to add Gemini-powered features (text, vision, multimodal) to a site or product.
Why it matters: The API choice sets your AI feature's quality, latency and cost ceiling. Ranges move quarterly, budget with the ceiling-before-build discipline and keep the vendor swappable.
CDN (Content Delivery Network)
A network of servers worldwide that caches and serves your static files from locations close to each visitor.
Why it matters: A CDN is the cheapest speed you can buy: images, scripts and pages arrive from nearby instead of from one distant server. Most serious sites treat it as standard infrastructure.
Quarterly, and only when the numbers move
Get the rate report before you negotiate.
Updated rate bands across the major stacks and regions, plus what changed and why. No other email.
Done reading definitions? Get a scoped quote, two minutes now, a written answer with price and timeline in two days.