Skip to content

Say what OpenBot is, and how to have us build it - #607

Merged
davidmckayv merged 1 commit into
mainfrom
docs/readme-positioning-and-gates
Sep 18, 2026
Merged

davidmckayv merged 1 commit into
mainfrom
docs/readme-positioning-and-gates

Conversation

@davidmckayv

@davidmckayv davidmckayv commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

The README opened on what OpenBot does for a Bot ("AI coworkers you can hand real work to… each gets a computer of its own"), which describes the machinery rather than the decision a reader is actually making. And the offer that closes most of these conversations was written down nowhere on this page.

What changed, all at the top

  1. Positioning. Leads with the frame we use in conversation: it is the assistant people already know how to use, and the difference that matters is that it runs on your infrastructure and you can change anything about it. The computer-per-coworker detail moves to the second line, where it supports the claim instead of opening with it.

  2. Two gates in the link row. "Talk to an engineer" and "Have us build it with you", ahead of the existing links.

  3. A third gate as a callout, after the "template, not a product" notes, where a reader has just learned they are expected to build it themselves: we will stand it up inside your infrastructure, customize it into something that looks like your product, and hand it back to you to keep changing.

On the links. They carry ?ref=openbot_readme, which the booking page has to inventory or it silently rewrites the ref to contact_us and every arrival from this repo folds into the contact-page default. That registration is website#584, so merge that first or the attribution is wrong from the moment this lands. The page itself works either way.

What this does not do. No competitor is named. Nothing contradicts the "a template, not a product / no hosted version to sign up for" note directly below: what is offered is engineers, not a SaaS, and the product still ends up yours to run and keep changing.

Companion PRs on the website: #583 puts OpenBot in the Products menu, #584 gives /openbot the same positioning and registers the ref.

Note: ## Deploy it still pins :v0.0.9 as its example tag and we are on v0.0.12. Left alone to keep this PR to the copy you approved; happy to fix it here or separately.

The README opened on what OpenBot does for a Bot, which describes the machinery rather than the
decision a reader is making. It now opens on the two things that actually distinguish it: it is the
assistant people already know how to use, and it runs on your infrastructure with everything about
it open to change.

The second half of that offer was written down nowhere. Somebody who wants this but does not want to
build it had no way to say so from here, so the top of the page and the end of the notes both carry
the way to start that conversation. The links use a ref the booking page inventories, so arrivals
from this repository are attributable to it rather than folding into the contact-page default.
@davidmckayv
davidmckayv merged commit 2d09a08 into main Sep 18, 2026
17 checks passed
@davidmckayv
davidmckayv deleted the docs/readme-positioning-and-gates branch September 18, 2026 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant