Have an agent team build your website

You don't build the site yourself, and you don't open a separate builder. You hire an agent in Crewdle, tell it what you need, and it builds, hosts and publishes the site with the Websites & apps tool. Your part is the part only you can do: say what you want, look at the preview, point at what should change, and say yes to the publish.

This guide follows one real run from start to finish: a one-page launch site for Northwind One, a wireless speaker from a fictional company, Northwind Studio. The page has a hero with a product render, three feature highlights, a specs strip and a waitlist form.

The result: a one-page launch site, built, hosted and published by a Developer agent.

Step 1: Hire a Developer, or a team

Open Marketplace in Crewdle and hire the Developer. The hire review shows its role and skills and lets you pick its model before you confirm. It arrives with the Websites & apps tool.

Hire the Developer: review it, pick its model, and confirm.

For a bigger project, hire the Software Team instead: an Engineering Manager with a developer, a code reviewer, a QA analyst, an architect and a DevOps engineer. You talk to the manager, and it first proposes a plan (steps, owners and estimates) that you approve before anyone starts. See Teams. After that, the steps below are the same.

Step 2: Brief it

Describe the site the way you would to an agency: what it is for, who it is for, the sections it needs, and anything that must be on it. Attach what you have, like your logo, photos or a product render. We asked for a one-page launch site with a hero using our render, three feature highlights, a specs strip and a waitlist form, and sent the real specs (360° sound, Bluetooth 5.3, Wi-Fi with AirPlay 2, 20-hour battery, 18 cm tall, 1.4 kg). If your organization has a brand kit, tell the agent which one to use.

The request lands on the Tasks board as a task with an estimate. If the agent needs a decision, it asks on a question card you answer with a click or your own words.

Step 3: Approve the hosting

A site needs somewhere to live. Before it builds anything, the agent asks your approval, on a card in the conversation, to set up the project's hosting environment. Approve it once. The environment then appears under Deliverables in the agent's Files panel, marked ready.

Step 4: Review the first version on a private preview

When the first version is built, the agent posts a private preview link and a short report: what is on the page, top to bottom, what it checked, and what it couldn't check. Nothing is published at this point. Open the preview and it appears beside the conversation, so you can read the report and look at the page at the same time.

Step 5: Comment with Feedback mode

Turn on Feedback mode in the preview header, then click anything on the page and type what should change. Each comment is pinned to its element with a number, and collects in a Feedback tray. We left two:

1. On the Join the waitlist button: "This button overlaps the top of the speaker. Move it above the image with a bit of breathing room."
2. On the features heading: "Keep this heading on one line on desktop."

The screenshots below are from a later round, with comments on the small line above the headline and on the header link.

Click an element to comment on it. Each comment is numbered and pinned to what you clicked.

The tray holds every comment until you're done. Send delivers them all to the agent in one message.

Click Send and the agent gets every point at once.

Step 6: Check the revised preview

The agent works through the list, rebuilds, and posts the updated preview at the same link, with each fix listed against your comment. It is still a preview: nothing is published until you say so. Look at both spots, and send another round if something is still off. You don't have to get everything in one round.

Step 7: Ask it to publish, and approve the card

When you're happy, say so. We wrote: "Both fixes look great. Please publish it." The agent then asks to publish, and an approval card appears in the conversation: Publish to the live site, promoting the current preview build to the project's public live site. Approve puts it live; Deny keeps it in preview so you can say what is missing. Nothing goes live without your yes, and if you step away, the conversation shows how many cards need you.

The publish waits on an approval card in the conversation, with the preview still open beside it.

Approve puts the site live. Deny keeps it in preview.

Step 8: It's live

Once you approve, the agent publishes, checks that the live page loads and matches the preview you approved, and sends you the address. Ours came with next steps: test the waitlist form once with our own name and email, an offer to make the sign-ups easy to view or export, and an offer to connect our own domain in place of the temporary address.

The site is live. The agent sends the address and what to do next.

We then asked the agent to look at the live site on screen. It opened the page in a desktop browser window, confirmed both fixes, and flagged one flaw we hadn't noticed: the render's background was slightly lighter than the grey hero behind it. It saved its screenshots to the Files panel and offered to fix the edge on the preview first, before anything changes on the live site.

The agent checks its own work: both fixes confirmed on the live site, one small flaw spotted, and a fix offered on the preview first.

Step 9: Find it and keep improving it

The site sits under Deliverables in the agent's Files panel, next to its hosting environment, with an Open button and a menu to download the project or copy its link. To change it later, just ask: "add a launch date", "swap in a new photo". The agent updates the preview, and asks before it goes live again.

Deliverables: the live site and its hosting environment, with the files you uploaded below.

What it costs

You pay per task, like any agent work, at the agent rate (1.5× the model's list price). Each request is its own task on the Tasks board, with the agent's estimate and what it actually spent: here, building the site, applying the feedback round, and publishing it. Set a monthly budget on the agent to cap what it can spend. See Credits and billing.

Every step of the site is a task on the board, with its owner, estimate and what it cost.