The $200 bill that started ComputerUse

Benjamin Boyce says he spent $200 on computer use in five days. His first response was frustration. His next response was to start building another option.

ComputerUse began with an ordinary piece of hardware: a ThinkCentre. Add another computer, a network switch and software that can manage access, and an idea starts to take shape. Give a customer a dedicated machine their agent can operate. Publish the price of the computer clearly. Let the customer understand which other costs are still their responsibility.

The idea is simple. Making it a dependable service is the work now underway.

One bill can contain several different products

“Computer use” can describe a whole stack of services. An AI model interprets a request and decides what to do. An agent framework manages the task. A desktop runs the applications. Storage keeps the files. Other services may supply browser sessions, proxies or paid application features.

Those components have different costs. A machine may be rented for a fixed period while the model is charged by usage. The same desktop can be quiet for an hour or generate many model requests while an agent works through a difficult task.

That is why Ben's reported bill is an origin story, not a pricing benchmark. We have not established the complete breakdown of that spending or a controlled comparison against the proposed ComputerUse service. Calling a $24.99 computer rental a replacement for $200 of mixed usage would leave out the information that actually matters.

What ComputerUse can aim to make simpler is the infrastructure line: which computer is assigned, what its base rental costs and how long that rental lasts.

The proposed model

The initial concept is one customer per physical ThinkCentre host, with a managed desktop environment. The proposed starting price is $24.99 per 30 days for an 8 GB host, with a $39.99 option on a 16 GB host. Each is planned with a 150 GB workspace allocation.

These are development-stage plans. Physical RAM is not the same as memory available to an application: the host, any virtualisation layer and the desktop operating system all need their share. ComputerUse must publish the usable allocation after the deployment design and machine testing are complete.

The entry tier is being designed around browsing and automation. The larger tier is being evaluated for heavier desktop work, including light video-editing workflows. Neither the RAM number nor a familiar computer brand establishes a performance guarantee.

A useful computer needs a clear lifecycle

A rental product is more than a remote screen. Customers need to know what happens when they close the browser, stop their agent, restart the desktop or cancel the rental.

Those are different events. A task can finish while the computer remains assigned to the same customer. Saved files may need to stay there for the next task. A deliberate workspace reset should require clear intent and remove the data covered by the stated policy. A machine should only become available to another customer after the previous customer's access has ended and the reset process has been verified.

Building those rules into the product early is part of the point. A clear bill is less useful if the customer cannot work out whether their files will be there tomorrow.

The agent should be a choice

ComputerUse is being designed with Boardly, OpenClaw and Hermes Agent connections on the roadmap. The intended role of the service is to supply a controllable computer. The customer's preferred software can organise the work and choose its model, subject to tested integration support and permissions.

That distinction matters for cost as well as flexibility. A computer rental should not be described as including unlimited reasoning from every model provider. Customers should see which charges are included, which services are optional and where the usage limits live.

What must happen before launch

The pilot needs to demonstrate a complete journey: a verified machine becomes available, an authorised customer receives access, a real task works, the correct rental is charged, and cancellation removes access reliably. The service also needs published storage rules and a tested process for resetting a machine before it changes customers.

The story began with a frustrating bill and two computers. The product will be measured by those ordinary, essential details.

Follow the ComputerUse build for verified milestones, documented limits and a clearer picture of what an agent's computer actually costs.