Web development agency
Your next client site, shipped
Someday is now. Agentic Assistants for your work draft the site, the ticket, and the client note. The Coder writes the code with you, the Product owner writes the issue, and Marketing drafts the update. You give the final go.
A first impression
A client site taking shape
- Your clients and their sites
- The pages and fixes that repeat
- Where you give the final go
Nothing is sent or shipped unless you asked for it or approved it, and money always asks.
The Coder writes the code. The Product owner writes the ticket. Marketing drafts the update. A send waits for your Approve.
A closer look
An idea goes in.
Real work comes out.
A client site taking shape. Explore how the pieces fit.
Illustrated workflow
02 / The team works
The team works
The assistants take the goal, use the ready prompts and skills, and do the work in the tools you connected.
How it works
From a goal to a result.
- 01
Set a goal
You say what done looks like: a ticket, a client, a deadline, or a draft.
- 02
The team works
The assistants take the goal, use the ready prompts and skills, and do the work in the tools you connected.
- 03
You approve the risky step
Anything that sends, publishes, ships, or charges waits for your Approve. Approve a kind of step once and that assistant remembers it, but money always asks.
- 04
You get the result
A pull request to review and a client note, both ready for your final go.
Example
Send the site review to your client
It sends to people, so it asks first.
The team
You, and the assistants.
You
You name the client, set the goal, and approve what reaches a client and what goes live.
Coder
Writes the page or the fix with you, checks it in the browser, and opens the pull request on its own. A merge or a deploy waits for your Approve.
Product owner
Writes the issue, keeps each client's backlog in order, and drafts the status update.
Marketing
Drafts the client update, the changelog, and the launch note. Sending waits for your Approve.
Integrations
The tools it starts with.
- GitHub
- Slack
- Gmail
- Google Drive
- Linear
- Notion
Built in
What your assistants can use.
Its own computer
Each assistant works on its own computer in StellarFirm cloud, set up with the tools its job needs, and hands you the files.
Roles you make yourself
Name a role we don't ship, say what it does and give it any of our skills or your own. Comes with Ultra and enterprise.
A running app beside the chat
The Coder starts the app it built and shows it live next to the chat, so you can click through it yourself.
Keep going until it is done
Say what done looks like and the Coder keeps going, up to ten more rounds, until the goal is met. /stop ends it.
Long jobs in the background
A big job starts at once and runs in pieces in the background, streaming back as it goes. You can stop it any time, and sends and spending still ask.
Follows up on its pull requests
Switch it on for a Coder and it takes on failing checks, merge conflicts and review comments on its own pull requests. Merges and replies still ask you.
Put the app it built online
When the Coder has built an app, it can put it online at an address like your-name.stellarfirm.app once you approve. You can take it offline again any time.
Pictures and short videos
Assistants make pictures and short videos on StellarFirm's studio account, and each answer tells you what the work used.
Ready to use
Prompts and skills.
Skills
- Implement a change
- Verify in browser
- Draft an issue
- Write a changelog entry
- Stakeholder status update
Ready prompts
Write the client homepage from this brief, check it in the browser at phone width, and open the pull request.
Write the status update for this client and hold it for my Approve.
Turn this request into an issue with acceptance criteria.
Questions
Before you join.
Start with your first assistant.
Leave your email. Invites go out every day until 27 October, and we'll write when your spot is ready.