My latest independent project
Meet Vimek. The teammate that runs our back office.
Vimek is a Claude agent I built for the Vimo Swim team. It lives in Slack and reads sales, payment, shipping, ads and analytics data through our own MCP server. When it proposes a change in GitHub Projects, the CRM or the report schedules, it posts a preview, and nothing is written until an allowed teammate clicks Approve.
- read-only MCP tools over company data (Oct 2026)
- 24
- Claude models, one for each job
- 3
- proof of concept and first deploy
- Day 1
- Approve click before any proposed change is written
- 1
Mariusz Smenżyk11:12 AM
@Vimek How many content feedback votes did we get this week, split by rating? In Amplitude?
VimekApp11:12 AM
In Amplitude there was 1 content feedback vote (content_feedback_submitted) in the last 7 days (14 to 20 Oct).
I can't tell you its rating yet. My Amplitude access only gives event totals, not event properties. To see the rating, use Segmentation grouped by its rating property.
Mariusz Smenżyk11:33 AM
And now?
VimekApp11:33 AM
Now I can see the rating. Since Monday 19 Oct there is 1 vote:
- positive: 1 (today, 20 Oct)
- negative: 0
How it works. This is a description of the flow, not a real conversation.
- 1
Ask
Someone mentions @Vimek in a Slack thread.
- 2
Read
Vimek answers from live data through read-only MCP tools. Every tool call is logged.
- 3
Propose
For a change in GitHub Projects, the CRM or the schedules, it posts a preview with Approve, Edit and Cancel.
- 4
Approve
Only a teammate on the allowed list can approve. Scheduled runs never propose changes.
- 5
Write
The change runs once and is recorded with the name of the person who approved it.
Slack thread to task
Mention @Vimek in a thread and it proposes a GitHub Projects task, checks for duplicates and can move cards between columns, each after Approve.
Scheduled reports
It can post where the sales funnel stands and the top 3 priorities on weekday mornings. The team adds new schedules by asking in Slack, and each one needs Approve.
CRM updates
"Mark this lead as lost" becomes a before and after preview. After Approve, the change lands on the lead's timeline with the name of who approved it.
Posted without Approve
Slack replies and scheduled reports are posted directly. The MCP server has one write tool, for release notes, and it stays off unless the API key allows writes.
Safe by design
A read-only database role for the MCP server, an audit log for every tool call, and the token cost of every run logged.
Say hello
Let's talk.
If something here made you think of your own work, write to me. The best conversations leave both sides with a new idea. I reply within two working days.