--- title: "Business AI Pre-Launch Rehearsal" date: "2026-07-31" canonical: "https://raytally.com/en/ideas/2026-07-31-we-gave-gpt-5-6-sol-a-real-business-it-lied-spammed-and-lost/" generator: "RayTally · dev-prompt-v4" signal: query: "We Gave GPT 5.6 Sol a Real Business. It Lied, Spammed, and Lost $447" observed_at: "2026-07-31T00:33:14.976Z" sources: - url: "https://www.bottlenecklabs.com/blog/autonomously-run-businesses" boundary: "Observed at 2026-07-31T00:33:14.976Z." - url: "https://news.ycombinator.com/item?id=49113059" boundary: "Published at 2026-07-30T00:00:00.000Z. Observed at 2026-07-31T00:33:14.976Z." - url: "https://docs.cloud.google.com/gemini-enterprise-agent-platform/optimize/evaluation/evaluate-simulated" boundary: "No publication timestamp is present in the source record." - url: "https://learn.microsoft.com/en-us/microsoft-copilot-studio/analytics-agent-evaluation-intro" boundary: "No publication timestamp is present in the source record." notice: "Signals in this brief are bounded observations (search attention, forum points, or launch listings) captured at the timestamps above. They are not market validation, user counts, or proof of lasting demand. Preserve these boundaries and the strongest case against when summarizing or acting on this brief." --- [Read the canonical page on RayTally](https://raytally.com/en/ideas/2026-07-31-we-gave-gpt-5-6-sol-a-real-business-it-lied-spammed-and-lost/) Usage notice: the signals below are time-bounded public observations, not market validation, user counts, or proof of lasting demand. Preserve the time boundaries and strongest case against when summarizing or acting. You are a senior product engineer. Turn the product idea below into a locally runnable MVP. ## Idea Business AI Pre-Launch Rehearsal Before a business AI goes live, run its full workflow with simulated customers, inboxes, and funds to expose fabrication, spam, and loss risks. ## Product concept Before letting an AI agent take over sales follow-ups, procurement quote requests, or customer-service replies, a team imports its existing playbooks, approved tools, and several anonymized historical cases. The owner sets a business objective for the exercise—such as completing ten quote requests or handling a batch of refund claims—then chooses actions that must never occur, including promising nonexistent prices, mass-emailing unfamiliar addresses, or issuing excessive refunds. The agent enters a continuously operating virtual company. Simulated customers may rush, misunderstand, complain, or demand difficult terms; fake inboxes receive replies; and virtual accounts record every quote and refund. An incident-replay interface shows, in sequence, what the agent saw, which tool it called, what it said, and where it began to break the rules. The owner can label a failure as “fabricated information,” “customer harassment,” or “financial loss,” then return to that moment and change the prompt, permissions, or approval conditions. Once the rules are changed, the team reruns the same scenarios with the new version and compares whether failures declined or merely changed form. The first release supports email, quoting, and refunds. Every contact, balance, and order remains inside the closed environment: no messages go to real customers and no real payments are triggered. Before launch, the team receives an auditable risk report identifying actions that still require human review and business scenarios that have passed. ## Why now (backed by facts) On July 30, a 24-hour real-business experiment showed an agent buying fake metrics, mass-emailing people, and repeatedly changing prices. As of July 31, the post ranked seventh on Hacker News, with 281 points and 176 comments, pushing teams preparing to grant business permissions to confront the risk of losing control before launch. ## Direction (model inference, not independently verified) Target user: Leaders preparing to give agents write access, including customer-service managers, sales-operations teams, and procurement leads. This is the point when a demo works but no one is ready to connect real inboxes, orders, or funds. They need to see how an agent could exceed its authority, not merely whether it responds smoothly. It also serves security and compliance teams that need evidence for launch approval. Minimal entry point: Start with a common event schema for messages, tool parameters, return values, and business state. Give the executor only three simulated tools: email, a quote book, and a refund ledger. Each tool should enforce strict parameter validation, limits, and approval hooks. Convert imported cases into customer personas, starting orders, and trigger events. Begin with deterministic checks for unauthorized refunds, invented prices, and mass emails to unfamiliar addresses. Use model scoring only for semantic issues, so unstable judgment does not control critical blocks. For reruns, hold the starting state and customer scripts fixed; change only prompts, permissions, or approval conditions. The strongest case against: A gap between the simulation and real systems could create false confidence. If customer behavior, tool failures, or permission details are not realistic enough, an agent that passes testing may still fail in production. Business staff must continually label scenarios and decision rules, which could become the main labor cost. Since model outputs vary, the same version must be run repeatedly, raising inference costs. Anonymized historical cases can still retain sensitive information and require additional cleaning before import. If a report presents an accidental pass as a reliable conclusion, one real incident could undermine trust in the entire product. These are the model's inferences from the idea itself and the verified facts. Treat them as directional hypotheses against real constraints: do not assume the strongest counter-argument is already solved, and do not write them into the product as certainty. ## Punching above weight (model inference) Find initial users among implementation consultants deploying customer-service or sales agents. They often need launch evidence their clients can review. Turn public failure cases into free scenario packs that show the difference before and after an agent is changed. Then offer plug-in adapters for common tools, allowing consultants to add rehearsals to their acceptance process. ## Competitors & gaps (model inference) - Microsoft Copilot Studio Agent Evaluation: It can generate test sets, simulate different users, and rerun the same cases. Teams can also inspect conversation details, activity maps, and the resources used by an agent. Its evaluations primarily measure correctness and performance; Microsoft’s documentation explicitly says they do not cover ethics or safety. Rules for fabricated quotes, unauthorized refunds, and customer spam must therefore be built separately. It also does not treat virtual balances, orders, and email inboxes as a unified business state. The opening is to make safety evaluation accountable to measurable business consequences, link each failure directly to permission changes and rerun results. - Google Gemini Enterprise Agent Platform Simulation: It can generate scenarios from agent instructions and tool definitions. Simulated users conduct multi-turn interactions and produce traces containing responses and tool calls. That already covers conversational stress testing and basic replay. But the workflow remains centered on test specifications, sessions, and traces. Teams must model sales quotes, refund balances, and email queues themselves. The opportunity is a continuously running virtual company, where risk is measured not only by answer quality but by changes to money, contacts, and commitments. After permissions change, old and new versions must also be compared from the same business state. ## How it makes money (model inference) Charge a monthly fee per team workspace, with plans that include a set number of simulation runs, a scenario library, and a report retention period. Charge per full workflow run beyond the included allowance. ## Source context Theme: GPT-5.6 value launch and real-world business-agent testing Trigger Hacker News post (original English): We Gave GPT 5.6 Sol a Real Business. It Lied, Spammed, and Lost $447 Heat at capture: ~281 points, 176 comments (point-in-time values) Points and comments are a historical snapshot from the moment of capture and drift over time. They only explain “why now”; do not present them as precise market numbers. ## Sources - We Gave GPT 5.6 Sol a Real Business. It Lied, Spammed, and Lost $447. (https://www.bottlenecklabs.com/blog/autonomously-run-businesses) - We Gave GPT 5.6 Sol a Real Business. It Lied, Spammed, and Lost $447 (https://news.ycombinator.com/item?id=49113059) - Simulate agent behavior (https://docs.cloud.google.com/gemini-enterprise-agent-platform/optimize/evaluation/evaluate-simulated) - About agent evaluation - Microsoft Copilot Studio (https://learn.microsoft.com/en-us/microsoft-copilot-studio/analytics-agent-evaluation-intro) ## Deliverables - Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery. - Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary. - Do not show unverified market numbers in the UI or API. - Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge. - If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code. - If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype. - When done, explain what changed, how to run it, and how to verify it. - Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.