The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Does someone on your team lose a day or two building the sales report every week or month?
That was the starting point at Mokobara, the premium travel brand. Pulling sales across all their stores, checking returns, reconciling the numbers and emailing each manager took 1 to 2 days every cycle, with 8+ hours of that spent just reconciling.
I built them an automation on Make.com a few months ago. It has run on its own ever since, weekly and monthly:
Make pulls every sales record from BigQuery, 100K to 250K per cycle. That is too many for one request, so it reads them page by page and stitches them back together.
It calculates the numbers the team actually uses: net sales per store after returns and discounts, return rates and the change against the last period.
It builds a CSV with the full breakdown and a short email summary you can read in 60 seconds.
It reads a Google Sheet of store representatives and emails every one of them the report for their own store.
The result: the reporting problem is gone. The report went from 1 to 2 days of manual work to fully automatic, and the 8+ hours of reconciliation dropped to zero.
Two things I would do the same way again:
Calculate "net sales" in the automation, not in the warehouse. The business rule for what counts as a net sale is not what the raw data stores.
Send people their slice, not the whole report. One report for everyone gets skimmed by everyone.
The figures in the image are placeholders, the real ones stay with the client.
What report is your team still building by hand? Tell me where the data lives and I will tell you how I would automate it.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Challenges
View all
Related posts
A workflow can finish successfully and still be wrong.
That is the reliability problem with production AI agents. A green execution only tells you the workflow ran; it does not tell you whether the model had the right context, chose the right tool, or returned a useful answer.
A practical n8n reliability loop:
• constrain inputs, tools, schemas and routing
• tag executions and inspect full agent logs
• run evals whenever prompts, tools or models change
• add real production failures to the test set
• monitor execution, quality, efficiency and safety separately
The best metric is not the one you can collect. It is the one that changes a decision.
Which failure would your current monitoring miss?
A pivot table isn't a report until someone can act on it in under 10 seconds.
I see plenty of "analysis" that's really just raw data with filters applied, technically correct, practically unusable. The person opening it still has to do the thinking the analysis was supposed to do for them.
If the takeaway isn't obvious at a glance, it's not finished yet.
AI is becoming useful for a simple reason: it’s starting to finish the work, not just suggest what to do.
For a small business, the difference is clear.
“How should I follow up with this lead?” is advice.
Researching the lead, preparing a personalized message and updating the client list is execution.
The opportunity isn’t replacing your team. It’s removing the repetitive steps that keep people away from customers and creative work.
What’s one task you would happily stop doing every week?