Your Website Must Be Open for Business

6 min read

Most Websites Stop Where Business Starts

20.08.2026, By Stephan Schwab

Most company websites stop exactly where business starts. They explain the offer, display a catalog, then hand the visitor a phone number or contact form. That was acceptable when simply being online made a company look modern. It is now a dead end. Cloudflare says automated bots generate roughly 57% of all web requests. That does not mean 57% of your customers are AI agents. It means the browser-shaped human is no longer the only visitor your digital presence must handle. AI systems already crawl vastly more pages than they return as human visits. A brochure gives them enough material to describe your company, but no reliable way to do business with it. The next version of your website must answer from current business knowledge, show real availability, prepare a quote, schedule an appointment, start an order, or resolve a service request. That means connecting the public website to CRM, calendars, inventory, billing, support, and the awkward old systems underneath. It also means identity, permissions, audit trails, failure handling, and ownership. In other words: software work, even if you do not sell software. An Embedded Delivery Partner or Forward Deployed Engineer helps the CEO and CTO turn that boundary into a working front office for humans and trusted agents. The prettiest brochure will not win. The business whose digital front door actually opens will.

Three eras of business websites: an early online brochure, a modern catalog requiring a phone call, and human and AI customers completing business online.

The Number Without the Nonsense

Automated traffic is 57% of web requests. That does not make 57% of your customers AI agents.

In July 2026, Cloudflare reported that automated bots generated roughly 57% of all web requests. That figure includes automated traffic beyond AI: search crawlers, monitoring, malicious bots, and other software making requests without a person clicking each link.

AI crawling is the sharper warning. Cloudflare’s crawl-to-refer data measures how many pages a platform fetches for every human visit it sends back. In July 2025, Anthropic crawled about 38,000 pages per referred visit, OpenAI about 1,091, and Perplexity about 195.

Those are not purchases. They show the old exchange breaking. Search engines crawled pages and sent people back. AI systems can consume the pages, answer elsewhere, and send almost nobody. Your website may influence the buying decision without receiving the buyer’s visit.

Being discoverable still matters. Traffic matters less as proof of business value. The harder question is whether a visitor with intent can act.

A Catalog Is Still a Brochure

A polished catalog that ends with “Call us for a quote” is a brochure with nicer CSS.

The first company website was a signal: we are modern because we are online. The next generation added catalogs, search, and glossy product pages. Yet many sites still stop before the transaction. Read the service description. Copy a product number. Call during opening hours. Explain everything again. Wait while somebody types it into another system.

Humans tolerate that nonsense because we have decades of practice compensating for badly joined systems. Software agents will simply favor businesses with a usable next step.

A digital front office lets a visitor:

  • get an answer grounded in current business knowledge
  • see real availability and pricing
  • submit an inquiry that becomes a complete CRM record
  • request an appointment against real calendars
  • prepare a quote, start an order, pay, or open a support case

Each action crosses from the public Internet into operations. That is the point. A brochure publishes the story. A front office moves the work.

One Business, Two Doors

Humans and agents need different interfaces to the same prices, policies, availability, and business rules.

People will keep reading pages, comparing alternatives, filling forms, and becoming annoyed by calendar widgets. Build those journeys well. The new Internet adds software acting for people. It needs structured information, explicit actions, predictable responses, and a trustworthy identity.

That means two doors into the same business:

  • human-readable pages and forms for people using browsers
  • machine-readable data and controlled actions for trusted software
  • one source of truth behind both
  • the same evidence when an action succeeds, fails, or needs approval

If the website says a service is available but the scheduling system says otherwise, you have two competing realities. An agent-friendly interface only lets the contradiction travel faster.

Open for business does not mean open to everyone. Some bots help people find you. Some train models. Some act for customers. Others scrape inventory, test stolen credentials, or hoard appointment slots. Cloudflare now separates search, training, and agent use in its controls. Its July 2026 agentic Internet announcement gets the boundary right: discoverability, content use, and authorized action are different decisions.

Your business needs the same separation:

  • public information without authentication
  • low-risk actions with validation and rate limits
  • customer data behind verified identity and authorization
  • consequential actions with confirmation, audit trails, and sometimes human approval

“AI-ready” cannot mean publishing an API key and hoping the future is polite. The controls are part of the product.

The Hard Part Lives Behind the Homepage

The homepage is not the transformation. The seam between systems is.

The CRM knows the customer but not current capacity. Inventory arrives through a nightly export. Pricing lives in a spreadsheet because the official system cannot express the exceptions. Three calendars disagree. Support knows which promises sales keeps making. Finance knows why the “simple” payment flow is not simple.

A website agency can make that landscape look coherent. A website builder can publish it faster. A chatbot can speak confidently about whichever fragment reached its knowledge base. None of those makes the business coherent.

Somebody must trace the real workflow, decide which system owns each fact, expose one useful action, handle exceptions, test the integration, deploy it safely, and leave the company able to change it.

Call the initiative a new website, customer experience, automation, or AI rollout. Underneath, it is software responsibility. Vendors can do the typing. They cannot remove your ownership.

Put Someone Inside the Gap

The useful role stays with the problem until one valuable action works end to end.

An Embedded Delivery Partner or Forward Deployed Engineer works with the CTO, not around them. The role sits where the organization chart fragments the problem: marketing owns the site, sales owns the CRM, operations owns capacity, finance owns payment, IT owns access, and a vendor owns implementation.

The work is concrete:

  1. Choose one action worth completing: qualify an inquiry, book a service, produce a quote, or check an order.
  2. Follow it through the real systems and the people repairing today’s gaps.
  3. Decide what humans and trusted agents may see and do.
  4. Build the smallest end-to-end path with tests, security, monitoring, and recovery.
  5. Put it in front of real users, fix what fails, and leave ownership inside the company.

That proximity makes the role useful: close to the workflow, the software, and the consequences. As The AI Workshop Will Not Ship argues, describing transformation is easy. Taking responsibility for the system is the job.

Start With One Door That Opens

Do not begin with “make the website agentic.” That phrase can fund an impressive amount of fog.

Begin with one customer intent the company handles badly today: requesting a quote, finding an appointment, confirming availability, opening a service case, or changing a delivery.

  • Can a human complete it online without switching to email or telephone?
  • Could trusted software complete or prepare the same action with explicit permission?
  • Do both paths use the same business rules and source data?
  • Can the company explain, audit, recover, and change what happens?

If the answer is no, you are not missing a widget. You have found the next piece of digitalization work.

Keep the brochure if it tells the story well. Just stop confusing the story with being open for business.

Talk It Through

Tell me what is happening. I listen, ask a few practical questions, and reflect back what I see: where the risk may sit, what may be blocking delivery, and what looks worth checking next. No pitch, no obligation. Confidential and direct.

Talk it through. Practical reflection, no pitch.

Start a Conversation

Newsletter: No methodology theater. No fluff.
Delivery insights and drama you won't find elsewhere.

×