I posted another couple of new Looker Studio dashboards in my Contra shop today and thought I would share some related eye candy with ya'll.
This is a bundle of four funnel and timeline data visualizations / infographics that I created specifically for Google Analytics e-commerce events.
I was inspired to create this after having stumbled upon a slough of similar GA4 ecommerce-related dashboards that were woefully visually unappealing. Creating more beauty in the world around me is one of my prime movers.
https://contra.com/products/mYxjErTV-ga4-ecommerce-funnel-visualization-pack
Make.com Level 5 & Zapier Expert: AI and Ops Automation
13
Followers
Make.com Level 5 & Zapier Expert: AI and Ops Automation
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 (http://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.
5
622
How do you automate a daily sales report from BigQuery to Slack with Make.com, when the data is 250,000 rows and the reader is not an analyst? Six decisions make or break it.
A direct-to-consumer brand's daily sales report took one to two days to compile, which meant Monday's numbers arrived on Wednesday. A 7 AM Make.com scenario now pages the data out of BigQuery, computes the KPIs and posts a plain-English summary to Slack and email before anyone opens a laptop.
The six decisions:
1. Page, do not pull. A day can be up to 250,000 rows. The scenario pages through BigQuery in chunks and aggregates as it goes, so no single step holds the whole table.
2. Compute the KPIs in the scenario, not in the prompt. Revenue, orders, average order value, top products and day-on-day change are arithmetic. The model only writes the sentences.
3. Give the model numbers, never the rows. A short structured summary goes to OpenAI with a fixed template; the output is two paragraphs a founder reads in thirty seconds.
4. Check before you post. If a KPI is null, if the row count is far below the trailing average, if a query failed, the scenario alerts the owner instead of posting a confident wrong report.
5. Post where people already look. Slack channel at 7 AM plus an email copy for the people not in Slack. No dashboard to remember to open.
6. Keep a paper trail. Every run logs the query window, row count, KPIs and the text it posted, so a number can be traced back a month later.
The diagram shows the run: schedule, paged query, KPI step, summary, checks, Slack and email. The full case study is on my profile. The same scenario shape works with Shopify, Stripe, a CRM or a Sheet as the source.
Prem Patel, Nex Automations. Make.com Level 5 certified, official Make partner, Zapier Certified Expert.
How do you show a client three website directions on one call without drowning in tabs?
This week we stopped juggling. We built a presenter page with Claude Code and ran the whole call from one tab.
The problem it solves: on a design call you open a tab per concept, resize the window to "show mobile", scroll hunting for the section you meant, and the client loses track of which version is which. The work was fine. The way we showed it wasn't.
What it does, all in one tab:
Direction tabs across the top. The real site runs inside a browser frame, so scrolling, hover states, animations and video all work live.
Desktop or Phone. Phone is a true 390 px view. Desktop renders the real 1440 px layout scaled to fit, so you see the actual design, not a squeezed one.
Full screen in one click, made for screen sharing.
Highlight buttons that jump the site straight to the section you are talking about: the opening, the work grid, the film.
A short page list (home, one project and contact), so the walkthrough has a beginning, middle and end.
The guardrail designers will appreciate: only 4 or 5 pages of each site open. The landing page, one full project and the key pages. Every other link shows "This page comes with the full build" instead of opening. You pitch the real thing without handing over the build before there is an agreement.
It travels too. Packed as a zip, it runs from a double-click with no server and no install, so our partner can run the same demo on his own calls.
Why not just send a staging link? It opens every page, and on a call the client wanders off on their own. This keeps everyone on the same screen.
What I would tell any designer pitching websites: show the site moving. Scroll, hover and motion are exactly what a PDF can't show.
How do you present website concepts today: a PDF, a Figma prototype or a live link?