Requests become clear tasks
Will writes the task with the context, the source and what counts as done.
Will
Right now, you’re the one turning customer requests into tasks.
Will turns requests that come in by email and from the team into clear tasks in ClickUp, tracks what’s blocked and looks after the integrations between Nuvemshop, Bling and the marketplaces. Through MCP, your AI tools know the company.
LLéoengineering
Hey Will, why did Mercado Livre orders stop coming into Bling?
Willdone
BlingSaw the integration stopped at 03:12
Mercado LivreFound 27 paid orders missing from Bling- BlingRenewed the access and imported the 27 orders
ClickUpLogged the cause and the fix in the task
Done.The integration’s access expired; the 27 orders are already in Bling. None delayed shipping. I’ll let you know if it drops again.
Example · Lume Casa (fictional), a home-goods online store with 38 people.
Today, without Will
Every back-and-forth becomes Will’s work.
This is the back-and-forth of an ordinary day. Will takes all of it on and tells you when it’s done.
Your day so far5back-and-forths
- Got a change request by email, with no details
- Asked Gabi what the customer wanted
- Wrote the task from scratch
- Explained the company’s context to the AI again
- Found out the task depended on another one
I’ll get it organized. You write the code.
What Will takes off your plate
Blockers surface
Stalled tasks show who can unblock them, and Will chases that person.
Integrations watched
When Nuvemshop, Mercado Livre and Bling stop talking to each other, Will notices, reconnects them and recovers whatever was left behind.
Status without a meeting
A summary of what moved, straight from ClickUp, with the links.
Your company inside Claude, Codex and Cursor
What Will knows, available to your AI tools via MCP, with Will’s permissions.
Quick guide
How to use AI on your development team: 5 practical uses
On a development team, AI helps you write tests and make sense of old code, but a lot of the time goes into the work around the code. Here are five places where Will takes care of that part, in ClickUp, Slack and email, so the team can stay in the code.
- Vague requests met with the right questionsWhen a vague request lands in ClickUp, Will asks the requester for the expected behavior, an example and how to test it. The card reaches the team ready to estimate.
- Customer context on the bugWhen a customer reports a bug, Will adds the order from Nuvemshop, the customer service messages and the steps the customer took to the card. Nobody has to ask for the screenshot again.
- Status updates without interrupting the teamWhen marketing or customer service asks "when does it ship?", Will answers from what’s in ClickUp, with the date and the source card. The dev team keeps working on what it was doing.
- Blameless incident reportsAfter a production issue, Will pulls the Slack messages, the alerts that came in by email and the timeline into a report with the cause, the impact and what changes. The focus is the process, not who made the mistake.
- A release checklistBefore each release, Will checks in ClickUp whether the tests passed, who reviewed it and what customer service needs to know, and tells each team when the version ships.
Through Will, Claude, Codex and Cursor get the context you now explain all over again in every conversation, within Will’s permissions: see how Will’s MCP works.
Work with Will
Will inside the system you use
Will works on the screen you already use, does the work and records every step.
ClickUpListBoardCalendar
| Task | Owner | Status | Due |
|---|---|---|---|
| Summer collection photos | Lia | In progress | Oct 9 |
| Collection pricing | Helena | Awaiting sign-off | Oct 8 |
| Gift set page | Léo | Stalled | Oct 7 |
| Campaign copy | Rafa | In review | Oct 10 |
| October storefront | Lia | To do | Oct 14 |
| Free shipping over R$300 | Gabi | In progress | Oct 13 |
| New checkout | Léo | In review | Oct 16 |
7 of 64 tasks in the list‹ 1 2 3 … ›
Gift set page
OwnerLéo
BlockerWaiting on Lia’s photos
ListLaunches
DueOct 7Oct 11YouWill
History
MonLéo marked the page as stalled
10:20Gabi asked Will for the change
10:21Will found the blocker: the photos
You work in the system, and Will stays beside you with the context.Will does it in the system and records every step. Browser inside Will
The features behind it
The parts of Will that do this work. Each one has its own page.
A day with Will
Example: Lume Casa (fictional), a home-goods online store with 38 people.
Today
L
Léoengineering
What does the "free shipping in southern Brazil" request need?
Will
From Gabi’s email: a shipping rule for three states, on orders of R$300 and up, effective in October. I wrote the task with that.
L
Léoengineering
Does it depend on anything?
Will
On the new Melhor Envio rate table, which arrives Thursday. It’s already linked in the task, and I’ll let you know when it’s in.
Example · fictional company and data
In the systems you already use
Nuvemshop- Bling
- Mercado Livre
Melhor Envio- ClickUp
Gmail
Use another system? If it has a login, Will uses it too. See all systems.
In what kind of company
Frequently asked questions
Does Will write code?
That’s not its focus. It organizes the work around the code: requests, context, blockers, integrations and status.
Does it work with GitHub or Jira?
Yes. Will works with ClickUp, Slack and your team’s email, and with your other development tools: if it has a login, Will uses it too.
What is Will’s MCP?
A server that lets Claude, Codex and Cursor use what Will knows about the company, with Will’s permissions. See AI tools and agents.
Where is the data kept?
The details are in Security and LGPD (Brazil’s data protection law).
Start with what you chase by hand.
Plans tailored to your company. Tell us what takes up most of your team’s day, and Will starts there.