Who we are
TWL is an Australian ecommerce retailer selling high-performance gear for functional fitness. We carry our own brand alongside Nike, Reebok, TYR, and dozens of others. We are roughly 25 people based in Australia, running four Shopify storefronts.
- Industry:
- Ecommerce
- Team size:
- ~25 people
- Time to value:
- Tuesday: 5 reports live
- Tools connected:
- ShopifyAsanaKlaviyoCin7SkuVaultSlackGoogle Sheets
From spreadsheet to daily report in 15 minutes
The first thing we gave Viktor was our daily P&L spreadsheet. It tracks revenue, marketing spend, gross margin, and daily profit against budget. Every morning someone had to open that sheet, read the numbers, and figure out where we stood. That was usually Andy, and it took about 15 minutes each day before the real work started.
Within 15 minutes of sharing the link, Viktor had reviewed the sheet, mapped every row, built a formatted report, and scheduled it to land in a DM at 7am. We asked for one adjustment, and it was done in a single reply. That report has run every day since.
It was not a demo. It was a working daily report built from a real spreadsheet, delivering real numbers, before the conversation was even finished.
Tools without connective tissue
We were not short on tools. We run Shopify, Cin7, SkuVault, Asana, Klaviyo, Google Sheets, and Slack across the business. The problem was scattered data. Answering a question like "what men's shorts do we have on order?" meant opening Asana, cross-referencing four Slack channels, and hoping someone had updated the ETA fields. Trade decisions were discussed in Slack but never logged. Delivery ETAs lived in one person's head. Nobody had the bandwidth to chase it all down every day.
Installed Saturday. Five reports live by Tuesday.
We had been wrestling with another AI tool for weeks trying to get automated workflows running. Viktor was installed on a Saturday, and by Tuesday we had five scheduled reports live. The difference was not just speed. Viktor read through our Slack history, understood what we were already doing, and proposed workflows that made sense for how we actually work.
Three workflows that started paying back immediately
The trade log audit
We have a shared spreadsheet where the team logs pricing and merchandising moves. In practice, decisions were made in Slack and never recorded. Viktor cross-referenced the log against weeks of Slack conversations, found three unlogged decisions on the first pass, and set up a daily audit that runs every weekday. It catches what is missing, nudges the owner, and follows up if nothing happens within 24 hours.
The Klaviyo weekly report
Ty, our email marketing manager, asked Viktor for a weekly report with open rates, click-through rates, revenue, and week-on-week trends. It now lands in our email channel every Monday morning with flags for underperforming campaigns. Before this, pulling that data meant logging into Klaviyo, exporting, and formatting it manually.
The delivery snapshot
Every Monday and Wednesday, Viktor audits our Asana product pipeline (30+ active purchase orders), cross-references four Slack channels for receipts and shipping updates, then posts a structured update. It flags risks, tags the people who need to act, and tracks action items through to resolution.
What changed once Viktor had memory
When we asked "what men's shorts do we have on order?", Viktor did not just search one system. It pulled data from Asana, cross-referenced delivery threads in Slack, matched them against warehouse confirmations, and flagged a projected stockout with the next restock five weeks away. We copied the entire response into our growth channel for the team. No reformatting needed. It was already the answer.
Anne, who manages our product pipeline, started using Viktor on her own:
“I'm using Viktor to find key notes on certain PO orders. No need to look for long threads or going to Asana.”
Anne
Product Pipeline Manager at TWL
That organic adoption matters more than any metric. It means the tool is genuinely useful, not just something one person is pushing.
12 workflows now running on autopilot
Three of these are entirely new workflows. Nobody was doing them before. They are not replacements for manual work — they are work that should have been happening but never did because nobody had the time.
Connecting Shopify next
We are connecting Shopify. That is the unlock we are most excited about. Once Viktor can read Shopify directly, the trade log impact reviews write themselves. We stop asking people "how did that pricing change perform?" and start telling them.
We are 15 days in, and we are still adding to the list. The pattern is clear: share a problem, get a working solution the same day, and wake up tomorrow with one less thing to chase.
