Customer story
Prompto sells leads per project. The morning check now runs before anyone opens Slack.
Targets live in Prompto's backend. Delivery lives in Meta. Joining them was somebody's first job every morning, and the one a holiday could skip.
Prompto
Proptech for new-build real estate. A marketplace, a sales platform and a 3D studio.
- Company
- Prompto, Ghent
- Industry
- Proptech, new-build real estate
- Team
- About 7 people
- Works in
- Slack
- Patricia since
- August 2026
- Connected
- Meta Ads, their own backend, Slack, Gmail, Calendar, Teamleader
In the channel
What it looks like on a Tuesday morning
She works where the team already is, so the output is a message in a channel. These are illustrations of the format, not screenshots of Prompto's channels.
An illustrated Prompto Slack workspace plays example conversations between the team and Patricia, one channel at a time. Pick a channel to read it at your own pace.
Morning. Meta check across 14 live projects, 4 worth a look:
- Two past 90% of target: still spending, so they are buying leads the client did not ask for
- One spending with nothing to show: four days, no leads, click-through halved
- One paused with room left: 60% of the target still to find
- One on tired creative: eight weeks old, cost per lead climbing
The problem
The morning check that nobody could afford to forget
Prompto is paid per qualified lead. Every project carries a monthly target the client sets, and its ads have to hit that without overshooting. Ad management is not a marketing task here. It is the bottleneck.
Two systems, matched by hand
Targets, leads sent and spend live in Prompto's backend. Impressions, clicks and cost live in Meta. Judging pace meant opening both and matching by eye, project by project.
A daily list with no room for a bad day
Switch the new month's ads on. Pause anything near target. Flag a project spending with nothing to show. Switch the paused ones back on. Every morning, every live project.
Every campaign waited on somebody checking it by hand
Not bad decisions. Confusion about what had already been done. A client's project never properly launched, or forgotten for a month, because the check lived in one person's head.
The rest of the busy work queued behind it
Call recaps, proposals, follow-up drafts, the chase when a prospect goes quiet. All of it arrives through Slack on top of the morning pass, and it grows with the client list.
What she runs
One coworker in Slack, reading both sides
Set up in Prompto's Slack in one working session, then given their own pacing rules rather than a generic ads playbook.
The daily Meta check
Set to run every morning over every live project. One short summary, numbered proposals: close to target, paused with room left, spending too much, not delivering, tired creative.
She proposes, a person approves
Pausing, activating and changing a budget each raise an approval card naming the ad set. Nothing changes until somebody says yes. A team can always allow one action for runs they start themselves.
She is in the room, and after it
Personal Gmail and Calendar are connected, so she joins the meetings and the recap, the decisions and the follow-up drafts land in Slack afterwards. Teamleader is connected too, for the quote and follow-up side of the account.
Context she keeps
She sits in the channels where the work is discussed and remembers what she is told. The account's history was loaded at setup, not retyped into every prompt.
The setup
Two systems had to agree before a decision was safe
An ads tool that only sees the ad account knows what a campaign spent. It cannot know whether the project behind it still needs leads. Prompto had that answer, in a different system, and joining the two was somebody's job every morning.
Meta Ads
Slack
ClaudePace
Target and delivery in one read. A project's position is an answer, not a comparison
Coverage
A new project in the backend with no campaign behind it is flagged on day one
Safety
Every write names the ad set on an approval card before anything changes
- Prompto's backend
- Their own MCP server, connected by their team. It carries the lead target, the leads sent and the spend per project. That is the half Meta cannot see.
- Meta Ads
- Their ad account, through Patricia's own reviewed Meta app. Reads run unattended. A write asks first, unless the team has always allowed that one action.
- Slack
- The check and every approval land in a channel the whole team can follow, not a dashboard one person remembers to open.
- Claude
- Their team also reaches Patricia from Claude, so the same context is there when they are building rather than operating.
What changed
What actually changed
Running since the middle of September 2026, so this is the shape of the work rather than a twelve-month trend.
The check no longer waits on somebody remembering
October is Prompto's first full month with it. That is the month that shows whether a holiday still decides what gets looked at.
Pace is one answer instead of two lookups
She reads the backend and the ad account together, so the question that needed two tabs and a mental join comes back as a list of proposals.
The team argues with her in public
The check lands in a shared channel, so a correction happens where the team can see it, and it goes back into the rules instead of one person's head.
FAQ
Questions about this setup
Can Patricia change Meta ads on her own?
By default, no. Reading is unattended. Pausing, activating and changing a budget each raise an approval card naming the ad set. A team can always allow one action for runs a person starts.
How does Patricia know what a project is supposed to deliver?
They connected their own backend as an MCP server, so the target, the leads sent and the spend come from their system of record rather than an estimate.
Does this only work if you have your own API?
No. The Meta side works on its own. Connecting your own system is what lets her judge pace against a target instead of only reporting spend.
How long did setup take?
The first session was about an hour. The rules that make the check useful were written over the next two weeks, from real calls and real corrections.
The same jobs, on their own pages
Budget pacing & alerts
A Slack alert the moment a client campaign is on pace to overspend, a CPA spikes, or budget is sitting idle, across Google Ads, Meta and TikTok.
See how she runs itThe daily pace check, described as a job rather than a story.
Creative refresh
A Slack heads-up the moment a client's ad starts to fatigue, with the metrics and a refresh brief already drafted.
See how she runs itSpotting the creative that has stopped working, which is one of the morning flags.
What this setup runs on
Meta Ads
The ad account the morning check reads, and proposes changes to.
Everybody deserves a Patricia.
She handles the work your team never gets to. You build the company. See what changes in your first week.