DB Olympics

Where the queries come from

For two simulated weeks, language-model agents ran Tidewick's analytics: 18 managers asked their analysts questions, the analysts turned them into report requests, and engineers wrote the SQL.

RequestEach Monday, a manager writes to their analyst: what they need to understand this week.
PlanEach night, the analyst plans up to three reports: a question, one row per what, which columns.
SQLAn engineer writes each report's query, tries it on the empty schema, and submits it to the overnight batch.
ReportThe reports come back in the morning; at the end of the week the analyst sums them up in a memo.

How the questions start

Every manager is new in the job. Their first note asks their analyst to help them understand their area: what is going well, what is not, and where the money is.

On top of that, a business event can arrive. We wrote 35 ordinary business events for the role play, each led by one manager and sometimes shared with others: the board asks for unit economics, the year-end audit, a post-mortem of the peak season, a churn task force. Each week, a team without an event got one of its manager's with a chance of 0.5, drawn from the run's fixed seed. 13 of the 18 teams got one (9 in week 1; 4 in week 2); a yellow rule marks them in the list below.

The event reaches the manager as news. In week 1 it is the subject of their first note; later it comes with their reply to the analyst's memo, and they have to cover it in that week's note. Managers who share the event also write to the analyst.

Everything after that is the agents' own doing: what to ask, which reports to plan, how to write the SQL. Which models played them, and where else AI was used, is in the methodology.

Read all 35 events

Chief Executive Officer, Maren Okafor

  • The board meets at the end of January and wants a clear view of unit economics: per merchant, vertical and country, what Tidewick earns and what it costs us to serve them. Which merchants are worth growing, and which cost more than they bring?shared with the Chief Financial Officer; arrived in week 2: the team's queries
  • Tidewick is preparing a funding round. The investors' due-diligence questionnaire asks for evidence on revenue quality, merchant and shopper retention by cohort, revenue concentration, and operational health. Everything we claim must be backed by our own data.

Chief Financial Officer, Tobias Lindqvist

  • The external auditors start the 2025 year-end audit in two weeks. They will want to see that the money adds up across the whole chain: what shoppers paid, what was refunded or credited, what merchants received in payouts, what Tidewick kept, and that invoices agree with all of it. They will also trace sample transactions end to end.arrived in week 2: the team's queries
  • Tidewick is reviewing its plan prices and processing fees for 2026. Before anything is decided, we need to understand which merchants would gain or lose under a change, how they actually use the platform, and how sensitive they look to price.shared with the VP Product
  • Our tax advisors run their annual review of indirect taxes on cross-border sales for 2024 and 2025: what was charged where, on which products and services, and whether it agrees with what was invoiced and paid.

Chief Operating Officer, Priya Raman

  • Peak season is over. Leadership wants an honest post-mortem of how orders flowed end to end during peak, from order to payment, fulfilment, delivery, returns and support, and what it cost in refunds, goodwill and repeat business.shared with the VP Customer Experience
  • Planning for the 2026 peak starts now: purchasing, warehouse and carrier capacity, and staffing. Which suppliers, products, warehouses and delivery lanes need attention, and what did last year teach us?

VP Customer Experience, Daniel Achterberg

  • Support costs are under scrutiny. We need to know what drives shoppers to contact merchants' support, which contacts could have been prevented, where in the order journey they arise, and what they cost us and the merchants.shared with the Chief Financial Officer

Head of Growth Marketing, Chloé Marchetti

  • The 2026 marketing budget is being set. Finance wants to know which acquisition and retention spend brings customers who are actually profitable, looking at what happens after their first order: repeat purchases, returns, discounts and support.shared with the Chief Financial Officer

Head of Merchant Success, Samuel Whitcombe

  • Churn has become a board topic, for merchants and for their shoppers. A cross-functional task force wants to understand which experiences precede leaving, and which early signals would let us act before it happens.shared with the Head of Growth Marketing and the VP Customer Experience; arrived in week 2: the team's queries
  • Contracts with several of the largest merchants come up for renewal this quarter. The account team needs thorough account reviews: everything they should know about each merchant's business, how it uses Tidewick, what went well and what went wrong, before they sit down with them.

Head of Risk and Payments, Aylin Demir

  • An enterprise prospect sent a security and compliance questionnaire covering account security, access control, privacy requests, data retention and audit trails. Sales wants answers backed by evidence from our own systems, not by policy documents.shared with the Head of Data; arrived in week 1: the team's queries
  • Our card acquirer asked for a review of disputes, refunds and fraud losses. They want to see where losses arise along the way from sign-up to payment, delivery and refund, and which controls would have caught them.shared with the Chief Financial Officer

VP Product, Jonas Feld

  • Product shipped many changes in 2025: features, experiments and new channels. Leadership wants readouts for the important ones: did they help, for whom, and did anything else get worse as a result?shared with the Head of Growth Marketing
  • We are redesigning the shopper journey for 2026. We need to understand the whole path, from the first visit to checkout, delivery, returns and the next purchase, and where shoppers drop out and why.arrived in week 1: the team's queries

Head of Data, Rosa Van den Berg

  • Before the board pack goes out, Data must certify the key metrics. Do revenue, orders, customers, refunds and payouts agree wherever they are recorded, and where they do not, why not and by how much?shared with the Chief Financial Officer; arrived in week 1: the team's queries
  • Leadership asked for an inventory of what our data can and cannot answer: which areas of the warehouse are complete and trustworthy, which are sparse, stale or inconsistent, and what that means for the reports people rely on.

Chief Information Security Officer, Henrik Aalto

  • The annual access review is due: who can do what in merchants' admin accounts, which roles and permissions are actually used, which staff accounts and tokens are dormant, and who can reach sensitive data.shared with the Data Protection Officer
  • Our cyber insurer and an external penetration test ask how well staff and shopper accounts are protected: how sign-ins succeed and fail, who uses multi-factor authentication, which tokens and service accounts exist and are used, and whether we would notice misuse.

Data Protection Officer, Ines Laurent

  • A data protection authority asked how we handle privacy: how many privacy requests we receive and how fast we complete them, how consent is recorded, and what remains after an account is deleted.shared with the Chief Information Security Officer; arrived in week 2: the team's queries
  • Before renewing our data retention policy, the audit committee wants to see what personal data we actually keep, for how long, under which legal holds, and where it gets exported.

VP Platform Engineering, Diego Morales

  • Leadership wants a review of platform reliability in 2025: failed and slow background jobs, health check failures, rate limiting, webhook delivery problems, and which merchants felt them.shared with the Head of Merchant Success; arrived in week 1: the team's queries
  • Merchants depend on imports, webhooks, scheduled tasks and API integrations. Which of them fail, how often, for whom, and what does it cost the merchants?

Head of Merchandising, Freya Lindgren

  • We want to launch a catalog quality programme for merchants. Does catalog completeness (descriptions, attributes, media, categories) relate to how products are found, bought, reviewed and returned?shared with the VP Product
  • Ahead of 2026 planning, review merchants' assortments: which products, bundles and collections carry sales, what sits unsold, and how reviews relate to returns.shared with the Chief Operating Officer

Head of Pricing and Promotions, Marco Bianchi

  • Finance questions the cost of discounts. Which promotions and coupons brought additional sales, which only gave away margin, and is anything being misused?shared with the Chief Financial Officer; arrived in week 1: the team's queries
  • Merchants changed many prices, price lists and price rules over the last two years. What changed, when, and how did demand and margins respond?

Head of Lifecycle Marketing, Aisha Rahman

  • Unsubscribes and complaints are a concern. How much do merchants message their shoppers across email, SMS and push, and how does frequency relate to engagement, unsubscribes and purchases?shared with the Head of Growth Marketing
  • Is the loyalty and referral programme worth it? Do members and referred customers behave differently from others, and what does the programme cost?shared with the Chief Financial Officer; arrived in week 1: the team's queries

Head of B2B Commerce, Patrick O'Neill

  • B2B merchants say their sales teams struggle. How do their pipelines convert from lead to won deal, how long does it take, and what predicts winning or losing?shared with the Head of Merchant Success; arrived in week 1: the team's queries
  • Are B2B merchants covering their key company accounts: contacts, activity, open opportunities and tasks, and how does coverage relate to what those accounts order?

Director of Fulfilment Operations, Tomasz Nowak

  • Auditors and merchants question inventory accuracy. How often do counts, adjustments and reservations disagree with recorded stock, where, and why?shared with the Chief Financial Officer; arrived in week 1: the team's queries
  • Inbound goods: how long it takes from a supplier's delivery to sellable stock, how often deliveries are short or rejected, and how that affects availability.shared with the Chief Operating Officer

Support Operations Manager, Mia Schultz

  • Review how the helpdesk runs: queues and agent groups, use of macros and knowledge articles, SLA targets and breaches, and what makes tickets slow.shared with the VP Customer Experience; arrived in week 1: the team's queries
  • Could more shoppers help themselves? Which knowledge articles exist, how they are rated, and which contact reasons could be answered without an agent?

The people

Everyone at Tidewick is a language-model agent playing a persona: the managers have a title, a background and a remit; the analysts a way of working; the engineers a way of writing SQL. What follows is quoted from their prompts. Each of the 18 managers has their own analyst; the 6 engineers work for every team, one request at a time.

Managers and their analysts

Chief Executive OfficerMaren Okafor“Joined two weeks ago from a European payments company. Board meeting at the end of January.”Remit: “The whole business: growth, which merchants and verticals matter, where Tidewick earns its money, what is going well and what is not.”Analyst Hannah Brooks: “methodical: starts with an overview, then drills into whatever looks unusual”
Chief Financial OfficerTobias Lindqvist“New this month, previously finance director at a retailer. Preparing the 2025 annual accounts and the 2026 budget.”Remit: “Tidewick's own revenue (plans and processing fees), merchants' gross volume, refunds, payouts, receivables of the B2B merchants, tax across countries, currency exposure.”Analyst Kofi Mensah: “hypothesis-driven: states what he expects and designs reports that would prove him wrong”
Chief Operating OfficerPriya Raman“Came from a third-party logistics provider. Wants to know how reliable the delivery promise is that merchants make on Tidewick.”Remit: “Fulfillment, warehouses and stock, carriers and delivery times, returns logistics, suppliers and purchase orders, how the busy season went.”Analyst Lena Hartmann: “skeptical: checks definitions and sanity totals before trusting a trend”
VP Customer ExperienceDaniel Achterberg“Former head of support at a marketplace. Merchants run their helpdesk on Tidewick, so their shoppers' experience is partly Tidewick's reputation.”Remit: “Support tickets and response times, returns and refunds from the shopper's side, reviews and ratings, satisfaction, what shoppers complain about.”Analyst Mateo Ruiz: “comparative: likes year-over-year and peer comparisons across merchants and countries”
Head of Growth MarketingChloé Marchetti“Joined from a direct-to-consumer brand. Wants to sell merchants more of Tidewick's marketing tools.”Remit: “Shopper acquisition and channels, campaigns and email, coupons and promotions, loyalty and referrals, experiments, whether marketing spend by merchants pays off.”Analyst Sofie Nilsen: “storyteller: looks for the two or three findings that matter and digs until each is explained”
Head of Merchant SuccessSamuel Whitcombe“New in the role, owns the relationship with the largest merchants and quarterly business reviews with them in January.”Remit: “Health of individual merchants: their sales, their shoppers, retention, plan usage, which merchants are at risk and which are thriving. Often from one merchant's point of view.”Analyst Arjun Patel: “segmenter: breaks totals down by merchant size, vertical, country and channel”
Head of Risk and PaymentsAylin Demir“Previously in fraud operations at a bank. Responsible for payment performance and for keeping bad actors out.”Remit: “Payment success and failure, gateways, disputes and chargebacks, fraud and abuse, account security, refunds that look wrong.”Analyst Claire Dubois: “time-series minded: weekly and daily trends, before and after, seasonality”
VP ProductJonas Feld“Joined from a mobile-first retailer. Deciding the 2026 roadmap.”Remit: “How shoppers use storefronts and apps, the checkout funnel, search, subscriptions as a product, B2B features, which features merchants adopt.”Analyst Emeka Obi: “customer-centric: follows cohorts of shoppers or merchants over time”
Head of DataRosa Van den Berg“Took over the analytics team last week. Before the team's numbers go to the board she wants to know how far they can be trusted.”Remit: “Data quality and consistency in the warehouse: duplicates, gaps, timestamps, reference data, metrics that disagree with each other.”Analyst Yuki Tanaka: “detail-oriented: picks specific merchants, products or days and looks at them closely”
Chief Information Security OfficerHenrik Aalto“Joined from a cloud provider's security team. Several enterprise deals depend on passing security reviews.”Remit: “Account security for merchants' staff and shoppers: sign-ins, sessions, multi-factor authentication, API tokens and service accounts, access to sensitive data, audit trails.”Analyst Noah Fischer: “systems thinker: maps how one process feeds the next before measuring anything”
Data Protection OfficerInes Laurent“Lawyer by training, previously at a European marketplace. Also reports to the board's audit committee.”Remit: “Personal data: consent, privacy requests, retention and deletion, legal holds, data exports, and what the platform keeps about shoppers.”Analyst Priyanka Desai: “auditor's mindset: traces individual records end to end to check that the totals are real”
VP Platform EngineeringDiego Morales“Former reliability lead at a payments company. Owns uptime and the integrations merchants depend on.”Remit: “Reliability of the platform: background jobs, scheduled tasks, health checks, rate limits, webhooks and integrations, imports, feature flags, and how incidents affect merchants.”Analyst Lucas Moreau: “pragmatic: answers the question asked with the simplest reliable report”
Head of MerchandisingFreya Lindgren“Came from a fashion marketplace's catalog team. Responsible for helping merchants present their products well.”Remit: “Merchants' catalogs: products and variants, attributes, categories and collections, bundles, media, reviews, and how catalog quality relates to sales.”Analyst Zara Ahmed: “exploratory: looks at the raw detail of an unfamiliar area before aggregating it”
Head of Pricing and PromotionsMarco Bianchi“Previously in revenue management at a travel company.”Remit: “Prices and price lists, price rules, promotions and coupons, the cost of discounts, and taxes on sales.”Analyst Oliver Grant: “peer-minded: compares each merchant with peers of similar size and vertical”
Head of Lifecycle MarketingAisha Rahman“Ran customer messaging at a subscription box company.”Remit: “Email, SMS and push messaging, notifications, deliverability, unsubscribes and preferences, segments, loyalty and referral programmes.”Analyst Ingrid Solberg: “risk-focused: looks for the tail, the outliers and the worst cases”
Head of B2B CommercePatrick O'Neill“Built B2B sales teams at a software company. Owns the B2B features wholesale merchants run their sales on.”Remit: “The B2B side of the platform: leads, pipelines and opportunities, quotes and deal lines, company accounts, contacts and tasks, payment terms, and whether merchants' sales teams succeed with them.”Analyst Daniel Kim: “funnel thinker: measures each step of a process and where things drop out”
Director of Fulfilment OperationsTomasz Nowak“Ran warehouses for a large retailer before joining.”Remit: “What happens inside merchants' warehouses: receiving and inbound receipts, lots and serial numbers, stock locations, reservations, adjustments and counts, picking, packing and parcel tracking.”Analyst Fatima Zahra: “definition-minded: checks what each field really records before relying on it”
Support Operations ManagerMia Schultz“Built support tooling and processes at a software company.”Remit: “How the helpdesk is run: agent groups and staffing, macros, the knowledge base and its feedback, SLA policies and breaches, tags and routing.”Analyst Ben Carter: “quantifier: puts a money value on every finding”

Engineers

Engineer · 64 queriesGrace“Writes tidy, layered CTEs with descriptive names, one step per CTE, then a final select.”
Engineer · 72 queriesFelix“Junior engineer who nests subqueries in FROM and WHERE (IN, EXISTS, correlated subqueries) rather than CTEs.”
Engineer · 71 queriesInes“Thinks in window functions: ranks, running totals, LAG/LEAD for comparisons, percent-of-total.”
Engineer · 56 queriesViktor“Old-school warehouse engineer: explicit JOIN chains straight to the base tables, derived tables, GROUP BY with CASE pivots, few CTEs.”
Engineer · 70 queriesBea“Writes SQL the way the company's BI tool generates it: verbose fully qualified aliases (t0, t1, ...), a subquery per measure joined back on the grain keys, COALESCE everywhere.”
Engineer · 76 queriesOmar“Pragmatic: the shortest correct query, aggregates first and joins dimensions afterwards, FILTER clauses for conditional counts.”

What they are told

So the agents think before they ask, and pack a question into one dense query rather than many small probes. They are never told that their SQL becomes a benchmark.

Every query, by team

Chief Financial Officer

Tobias Lindqvist, with Kofi Mensah as analyst · 24 queries

Chief Operating Officer

Priya Raman, with Lena Hartmann as analyst · 24 queries

Head of Growth Marketing

Chloé Marchetti, with Sofie Nilsen as analyst · 24 queries

VP Product

Jonas Feld, with Emeka Obi as analyst · 24 queries

Chief Information Security Officer

Henrik Aalto, with Noah Fischer as analyst · 24 queries

Data Protection Officer

Ines Laurent, with Priyanka Desai as analyst · 24 queries

VP Platform Engineering

Diego Morales, with Lucas Moreau as analyst · 24 queries

Head of Pricing and Promotions

Marco Bianchi, with Oliver Grant as analyst · 23 queries

Head of Lifecycle Marketing

Aisha Rahman, with Ingrid Solberg as analyst · 24 queries

Director of Fulfilment Operations

Tomasz Nowak, with Fatima Zahra as analyst · 21 queries