Convert an ADF mapping data flow into dlt and dbt and prove parity
Order or customer reporting still comes from an Azure Data Factory mapping data flow whose logic lives only on the ADF canvas, with no tests or review.
- Transformation
- Any domain
Platform
112 RecipesDuckDB
Recipes that can execute against local DuckDB.
The sandbox is seeded on DuckDB.
Re-engineer something you own 12
Backfill a bounded date range after a logic change without a full refresh
A business rule in an incremental model was corrected, and only a known date range of published history should be restated.
- Transformation
- Any domain
Convert a full-refresh dbt model to incremental and show the runtime delta
A dbt model is correct but a full refresh is too slow or too expensive to run routinely, and gets slower as history grows.
- Transformation
- Any domain
Refactor dbt models without changing consumer output
A model has grown into one long query with logic packed inline, and nobody dares change it because dashboards and reports depend on its output.
- Transformation
- Any domain
Convert a legacy SQL script or view into a dbt model and prove parity
A report or table is still produced by a hand-run SQL script or a database view outside dbt, with no tests, lineage or review.
- Transformation
- Any domain
Replace a Fivetran or Airbyte connector with a dlt pipeline and reconcile the result
A managed connector's bill changed shape, or it broke and the vendor fix has been pending for weeks, and the team wants the load in code it owns.
- Ingestion
- Any domain
Convert a notebook transformation into a dbt model and prove parity
A table or report is still produced by running a notebook by hand, pulling warehouse data into dataframes, with no tests, lineage or review.
- Transformation
- Any domain
Convert a scalar SQL function into a dbt macro and prove equivalence
Models or views call a scalar function created directly in the warehouse, so dbt cannot see the dependency and changes to it are not reviewed or tested.
- Transformation
- Any domain
Convert a hand-written history routine into a dbt snapshot and prove history parity
A Type 2 dimension is kept by a hand-written MERGE procedure or trigger that nobody wants to maintain.
- Transformation
- Any domain
Convert a Spark ingestion notebook into a dlt pipeline and reconcile what it lands
A Spark notebook lands raw files into bronze, and the team wants that load as tested pipeline code without keeping a cluster for it.
- Ingestion
- Any domain
Add a breaking data contract change as a new version beside the old one and revise its named consumers
A required change to a published relation's grain, column meaning or shape cannot keep the old interface.
- Transformation
- Any domain
Rebuild an exported visual ETL mapping as dlt and dbt and prove parity
A load into a fact or reporting table still runs from a mapping built in a visual ETL tool, and its lookups, filters, routing and insert-update-delete rules are visible only on the tool's canvas.
- Transformation
- Any domain
Build something that is not there yet 94
Land a SaaS or REST API into bronze with an incremental cursor and a schema contract
An API source has to load into bronze incrementally instead of reloading everything on every run.
- Ingestion
- Any domain
Build AML monitoring features at account-day grain
A transaction-monitoring model is fed hand-built features nobody can reproduce, so two runs on the same data disagree.
- Transformation
- Any domain
Build loan delinquency roll rates and vintage curves from loan, schedule, payment and event records
Credit risk reads delinquency off a servicer status field that each system refreshes on its own day, so bucket counts and roll rates differ from report to report.
- Transformation
- Finance
Build current-state tables from exported database change events
A batch export of database change events is available and the current state of its tables has to be rebuilt without reading the source database again.
- Ingestion
- Any domain
Preserve business-effective history and what was known at each reporting cutoff
A backdated correction must change today's reading of the past, yet a report issued earlier has to stay reproducible as it was published.
- Transformation
- Any domain
Build a business-event fact with auditable duplicate handling
Transaction feeds overlap, and source deliveries may be counted as separate business events.
- Transformation
- Any domain
Reconcile sell-in, sell-out and channel stock in a distributor ledger and a market view labelled by feed coverage
Sales ops, demand planning and channel finance each report a different sell-in, sell-out and channel stock figure, because distributors report in different units, codes and cutoffs.
- Transformation
- Supply chain and operations
Build manufacturer gross-to-net revenue with trade accruals and settlements
Revenue accounting closes the month by working gross to net in spreadsheets, nobody can audit them, and the trade accrual never ties to what customers claim.
- Transformation
- Finance
Measure trade-promotion lift and the post-promotion dip against an explicit baseline
Trade marketing reports promotion results with whatever comparison each analyst chose, and nobody can say what "without the promotion" meant for a given event.
- Transformation
- Revenue operations
Shelf-life exposure and first-expiry allocation eligibility by lot, location and open order line
Planners cannot see which lots are close to expiry, how much of each is still usable, or how much will go unallocated, so stock is written off that a customer could have taken.
- Transformation
- Supply chain and operations
Unify consent and communication preferences with auditable latest-wins logic
A customer who opted out in one system still gets messages from another, because each source says something different and whichever job ran last wins.
- Governance and cost
- Any domain
Compute historical customer lifetime value with margin
The payback conversation uses a customer value from a spreadsheet nobody can reproduce, and it counts order revenue only, with no refunds and no cost of serving the orders.
- Transformation
- Finance
Build retention cohorts and a churn feature table
Marketing, finance and product each quote a different churn rate because each defines an active and a lost customer differently.
- Transformation
- Any domain
Score customers with RFM, maintain segments incrementally and explain every move
Marketing segment lists come from a spreadsheet or BI export nobody can reproduce, and the same customer lands in different segments depending on who pulled the list.
- Transformation
- Any domain
Load a database table set into bronze with a bounded incremental strategy and landed-data proof
An operational database's tables have to land in bronze, and reloading every table in full on each run is too slow or too heavy on the source.
- Ingestion
- Any domain
Add dimension history with verified historical fact classification
Customer, asset or vendor attributes change, but past events need a defensible historical classification.
- Transformation
- Any domain
Explode an effective-dated bill of materials into component requirements
Component demand for an approved quantity of finished goods is worked out by hand or in a spreadsheet, and nobody can show which BOM revision, unit conversion or scrap rate produced a figure.
- Transformation
- Supply chain and operations
Build historical event amounts from effective-dated business rules
Historical fees or surcharges change when a current rate is applied to past events.
- Transformation
- Any domain
Build auditable event-to-resource attribution
Revenue or productivity must be reported by employee, asset or team, but responsibility for each event is unclear.
- Transformation
- Any domain
Load a recurring file drop into bronze with file-completeness and schema controls
A partner or vendor drops files into a folder on a schedule, and bronze has to pick up each delivery without a rerun loading it twice.
- Ingestion
- Any domain
Age payables from open items as of any chosen date and reconcile the total
Finance needs the aged payables for a past month or quarter end, but the payables system only shows what is owed today.
- Transformation
- Finance
Age receivables and compute DSO from open invoices as of any chosen date
Finance needs the aged receivables report and DSO for a past month or quarter end, but the receivables system only shows what is open today.
- Transformation
- Finance
Compare budget and forecast to actuals at cost-center grain
Budget-versus-actual is a monthly copy-paste from the general ledger into the budget spreadsheet, and the variances change depending on who built them.
- Transformation
- Finance
Detect duplicate invoice candidates from explicit matching rules before payment
Accounts payable paid the same supplier invoice twice and only found out when the supplier returned the money.
- Data quality
- Finance
Build a fixed-asset register and reconcile its net-book-value roll-forward
Every month someone rebuilds the fixed-asset register and depreciation schedule in a spreadsheet to prove that opening value plus additions less depreciation and disposals equals closing value.
- Transformation
- Finance
Tie the general ledger to its subledgers and classify every break
Month-end close stalls because control accounts do not agree with their subledgers and the difference is worked out by hand in a spreadsheet.
- Transformation
- Finance
Explain gross-margin change with a reconciled price, volume, mix, and cost bridge
Finance subtracts one period's gross margin from another and writes the explanation by hand, and the story changes with whoever builds it.
- Transformation
- Finance
Generate the revenue-recognition schedule and deferred-revenue roll-forward from contracts
Revenue is spread across months by hand in a spreadsheet and never agrees with the deferred revenue balance or with what was invoiced.
- Transformation
- Finance
Build a thirteen-week cash plan with traceable scenario assumptions
The weekly cash view is a spreadsheet rebuilt by hand each week, and nobody can say which receipt, payment or assumption moved a week's balance.
- Transformation
- Finance
Produce the trial balance and close pack as code
The close pack is rebuilt by hand every period and last quarter's trial balance cannot be reproduced as it was when the period closed.
- Transformation
- Finance
Allocate cloud and platform spend to teams and flag untagged cost and daily spikes
The cloud bill grew and nobody can say which team or product drove the increase.
- Governance and cost
- IT and FinOps
Measure SaaS licence utilisation and shelfware against contracts and invoices
A SaaS renewal is due and nobody can say how many of the paid seats are actually used.
- Governance and cost
- IT and FinOps
Promote a spreadsheet or CSV to a governed, tested table
A spreadsheet that reports and models depend on is edited by hand, and a moved, renamed or retyped column keeps breaking them quietly.
- Ingestion
- Any domain
Reconcile billed claims to payer remittances, denials and batch payments by payer
The revenue cycle team matches payer remittances to billed claims by hand, and nobody can say, payer by payer, how much of what was billed was paid, adjusted, denied or is still open.
- Transformation
- Finance
Build a thirty-day readmission cohort with explicit exclusions
The quality team rebuilds a readmission rate from a spreadsheet each quarter, and nobody can say who was left out of the rate or why.
- Transformation
- Any domain
Build nightly occupancy, ADR and RevPAR by property with closed-night restatements
Occupancy, ADR and RevPAR differ between reports because each one counts stays, comps, out-of-order rooms and cancellations its own way.
- Transformation
- Any domain
Deduplicate customers into a golden record with a source crosswalk
The same customer exists in several systems under different ids, so customer counts and per-customer revenue are inflated.
- Transformation
- Any domain
Standardize names and addresses and mint deterministic match keys
The same customer is written differently across CRM, billing and support, so joins on name or address miss.
- Transformation
- Any domain
Author an incremental dbt model with its contract and prove idempotency
A new dbt model must be brought up to date incrementally on each run, and nobody can show that a rerun or a re-delivery of records already applied leaves it unchanged.
- Transformation
- Any domain
Build paid and incurred claims loss triangles by accident and development period
Reserving analysts rebuild loss triangles by hand in spreadsheets, and a late payment or reserve change pushes back into cells that were already reported.
- Transformation
- Finance
Trace a recalled input lot to affected shipments and flag unreconciled runs and lineage that cannot be traced
A raw material lot is recalled and nobody can say which finished lots and which customer shipments contain it, or how much of it each holds.
- Transformation
- Supply chain and operations
Value inventory movements, closing stock and cost of goods sold under an approved costing policy
Finance cannot say what closing inventory is worth or how much cost of goods sold a month carries because receipts, issues, returns and adjustments are costed by hand.
- Transformation
- Finance
Build clinical-trial enrollment and site-performance models with every screened subject accounted for
Clinical operations rebuilds enrollment and site performance in a spreadsheet each month, and nobody can say who was left out of the enrolled count or why a site looks slow.
- Transformation
- Any domain
Build fleet utilisation against explicit asset availability
A fleet dashboard labels observed vehicle occupancy as utilisation without an authoritative available-time denominator.
- Transformation
- Supply chain and operations
Build lane-day on-time transport performance with open trips and exceptions shown as approved
A TMS dashboard reports on-time performance by lane, but nobody can inspect how it is calculated or reproduce its figure.
- Transformation
- Supply chain and operations
Build overall equipment effectiveness and a downtime Pareto
Plant OEE comes from a hand-built spreadsheet and nobody can say whether stops, slow running or scrap cost a line its points.
- Transformation
- Supply chain and operations
Reconcile production-order movements into work in progress by operation, first-pass and final yield, and exceptions
Yield and work in progress come from a spreadsheet that counts a reworked unit as a second unit produced and cannot keep first-pass yield apart from final yield.
- Transformation
- Supply chain and operations
Reconcile production-order standard cost to actual by element, with variance effects, overhead absorption and exceptions
Production-order variances are worked out in a spreadsheet nobody can audit, and nobody can say which standard version each variance was measured against.
- Transformation
- Finance
Reconcile components held at a subcontractor and processing charges to delivered work, with exceptions and coverage
Nobody can say how much of the company's material is sitting at a subcontractor, because transfers, returns, scrap reports and finished receipts live in different places and are never netted.
- Transformation
- Supply chain and operations
Build fully loaded acquisition cost and contribution payback by customer cohort
Marketing says a channel pays back quickly and Finance says it never does, and nobody can show the sum from the spend and contribution records.
- Transformation
- Finance
Attribute conversions to touchpoints under several models side by side
Marketing and Sales each have a spreadsheet crediting their channel with the same revenue, and together they claim more than was booked.
- Transformation
- Revenue operations
Build a campaign-day budget pacing ledger against versioned flight plans
Campaign owners ask whether a campaign is on pace and the answer changes with which budget version and which cost number someone used.
- Transformation
- Finance
Build cross-channel contact-pressure and send-eligibility decisions for planned contacts
The same person is emailed, texted and pushed by several tools in one week, and nobody can say whether the next planned contact is allowed.
- Transformation
- Revenue operations
Resolve B2B account hierarchies and roll measures to the ultimate parent
Sales and finance cannot see total revenue or pipeline for a whole corporate family because subsidiaries sit as separate accounts.
- Transformation
- Revenue operations
Conform product and SKU hierarchies across systems
The same product carries different SKUs and category trees in the ERP, the web shop and the point of sale, so sales by category disagree between reports.
- Transformation
- Supply chain and operations
Build a metric with explicit eligibility and reconcilable rollups
A new percentage, rate or average needs a defensible eligible population and missing-value policy.
- Transformation
- Any domain
Define governed metrics as a MetricFlow semantic model over a gold mart
Revenue or average order value means different things in different marts and dashboards, and nobody can say which number is right.
- Semantic layer
- Any domain
Build state durations by entity, location and reporting period
Waiting, idle, available or busy time must be measured by site or zone and hour from operational event histories.
- Transformation
- Any domain
Reconcile inventory positions across warehouse, ERP and physical counts and give every difference a reason
The warehouse system, the ERP and the last stock count report different quantities for the same item and nobody can say which is right or why.
- Transformation
- Supply chain and operations
Measure on-time-in-full delivery by customer, carrier and plant
Customers report late deliveries, and Sales, Supply Chain and the carriers each quote a different on-time-in-full figure because each applies its own promise date, tolerance and partial-shipment rule.
- Transformation
- Supply chain and operations
Build the procurement spend cube and flag invoice lines on or off contract
Procurement, Finance and the business units each quote a different spend total, and nobody can say how much was bought outside a contract.
- Transformation
- Supply chain and operations
Build order-line contribution margin with order and period rollups after refunds and returns
Gross sales minus original item cost overstates order margin because refunds and returns arrive after the order.
- Transformation
- Finance
Measure attrition, tenure and hire-cohort retention from the headcount outputs
Leadership asks whether attrition is rising and where, and nobody can answer from one consistent set of figures.
- Transformation
- People
Build period-end headcount and FTE by org and a roll-forward that ties every period
HR, finance and the board deck each report a different headcount for the same month-end, and nobody can say why.
- Transformation
- People
Check pay against salary bands and report pay gaps at an aggregate grain
A pay-equity review is due and worker-level compensation cannot be shared widely.
- Governance and cost
- People
Tie payroll to the general ledger at every cut-off and classify every break
Payroll expense in the general ledger does not match the payroll register at close, and the gap is worked out by hand.
- Transformation
- People
Build a training dataset that uses only information available at prediction time
A model scores well in training but worse in production because training rows used facts, corrections or labels a real prediction could not have seen.
- Transformation
- Any domain
Build the open purchase commitment balance and a roll-forward that explains every cutoff
Procurement and finance are asked what is still owed to suppliers on open orders at a month-end, and each answer comes from a different spreadsheet.
- Transformation
- Finance
Reconcile negotiated procurement savings to realized invoice prices in a traceable savings ledger
Procurement reports savings from negotiated agreements and Finance cannot trace them to the prices actually paid.
- Transformation
- Finance
Accrue supplier rebates from purchasing contracts and reconcile settlements
Procurement cannot say how much supplier rebate has been earned under each purchasing agreement this period, or how much of it suppliers have already credited.
- Transformation
- Finance
Match purchase orders, receipts and invoices line by line with an exception ledger
Accounts payable is asked to release payment and cannot say how much of an invoice is covered by the goods actually received.
- Transformation
- Finance
Sessionize event streams and build reproducible funnels from batch exports
Product analytics numbers cannot be reproduced outside the vendor's screen, and nobody can say why two conversion figures differ.
- Transformation
- Any domain
Track grant funds per award from authorization to drawdown and flag exceptions
Grants accountants cannot say per award how much is authorized, obligated, spent and drawn, and each report gives a different answer.
- Transformation
- Finance
Reconcile consignment stock by owner and the amount owed to each supplier when their stock sells
A supplier owns stock until it sells, that stock shares a store and SKU with stock we bought outright, and the stock report adds the two together.
- Transformation
- Finance
Reconcile marketplace orders to net payouts and held reserves by order line and settlement cutoff
Finance cannot say what each marketplace order settled for or what is still owed, because fees, refunds, chargebacks and reserves are netted into payouts.
- Transformation
- Finance
Settle store till sessions to counted cash, tender mix and deposit slips with an explicit over or short
Stores count each till at shift close and Finance cannot tell which shortages are real and which come from how the POS records voids, refunds, change and float moves.
- Transformation
- Finance
Reconstruct available-to-promise stock by SKU, location and cutoff from reservation and fulfilment events
Customer service promises stock that is already reserved, or sells the same units twice because reservations that expired or shipped still count against availability.
- Transformation
- Supply chain and operations
Build sell-through and stockout risk by store, SKU, and day
Planners cannot tell which items are about to run out because sell-through and stock-outs live in spreadsheets, and each one counts a day with no stock differently.
- Transformation
- Supply chain and operations
Tie bookings to billings to cash and classify every break
RevOps and Finance each quote booked, billed and collected, and the three numbers never agree because every team ties them together with its own spreadsheet.
- Transformation
- Revenue operations
Build a periodic opportunity pipeline snapshot with stage conversion and slippage
The CRM overwrites opportunity stage, amount and close date, so past pipeline cannot be reproduced as it stood at an earlier point.
- Transformation
- Revenue operations
Build commission-eligible bookings and quota attainment from explicit plan rules
Reps, managers and finance disagree on attainment because each team credits bookings with its own spreadsheet logic.
- Transformation
- Revenue operations
Build the MRR waterfall with net and gross revenue retention
Finance, RevOps and the board each quote a different net revenue retention because each turns subscriptions into monthly recurring revenue its own way.
- Transformation
- Finance
Build a sales commission payout ledger with accelerator tiers, caps and clawbacks
Finance cannot say what each rep is owed because tier rates, caps, holds, payments and cancellations are applied by hand in a spreadsheet.
- Transformation
- Revenue operations
Score submitted sales forecasts against realized bookings by forecast horizon
Leaders submit a sales forecast every week, but nobody can say how close each submission came to what booked, or whether the misses run over or under.
- Transformation
- Revenue operations
Build an auditable lead-to-account-to-opportunity lifecycle that counts deals and new customers once
Leads, accounts, contacts and opportunities sit in separate CRM tables and the conversion links are patchy, so nobody can show which lead became which customer or deal.
- Transformation
- Revenue operations
Reconcile accepted quote versions to orders and invoices with a price-exception ledger
Sales and Finance disagree about the price a customer was promised, and someone reconciles quotes to orders and invoices by hand.
- Transformation
- Revenue operations
Track ticket SLA attainment and backlog aging outside the vendor dashboard
The ticketing vendor's dashboard reports SLA met or breached, but nobody can check how its numbers are calculated.
- Transformation
- Service
Build one shared calendar and fiscal-period date table
Two reports put the same day in different weeks, months, quarters or fiscal periods because each mart builds its own date logic.
- Transformation
- Any domain
Normalize multi-currency amounts to a reporting currency with as-of rates
Finance adds amounts held in several currencies as if they were one, or restates old transactions at today's rate, and the total changes every time someone reruns it.
- Transformation
- Finance
Build shift revenue, cost and margin with reconciled rollups
A fleet dashboard reports revenue per shift but cannot establish whether a shift covers its applicable costs.
- Transformation
- Supply chain and operations
Declare source freshness SLAs and make stale data fail before downstream work
A load stopped and nothing failed; downstream models rebuilt on old data and the reports still looked current.
- Data quality
- Any domain
Land call-detail batches and aggregate them into subscriber-day usage with manifest completeness
Monthly subscriber usage differs by who ran it, because nobody can say which call-detail batches had landed or whether each arrived complete.
- Ingestion
- Any domain
Calculate rated usage charges with allowances, tiers, credits and restated corrections
Usage charges differ by who calculated them, because graduated and volume pricing, shared allowances and credits are applied differently from one run to the next.
- Transformation
- Finance
Reconcile meter reads to bills and quantify unbilled energy
Revenue assurance compares metered usage with billed usage in a spreadsheet each month, and nobody can say which differences are real and which are timing, estimates or a meter swap.
- Transformation
- Finance
Prove a change is safe before you ship 1
Assess an existing dbt change for safe merge without modifying it
An existing dbt change builds successfully but reviewers still need evidence that its business answers remain valid.
- Data quality
- Any domain
Explain a number after you shipped 1
Attribute warehouse spend to the models and job runs behind it, keeping idle and untied cost visible
The warehouse bill keeps growing and nobody can say which models or jobs are behind it.
- Governance and cost
- IT and FinOps
Work across more than one platform 4
Assess a Synapse dedicated pool or SSIS estate for a Fabric rebuild and recommend whether to go
A Synapse dedicated SQL pool or a set of SSIS packages is due to move to Fabric, and nobody can say what is in it, what each piece would take or what stops it.
- Re-engineering
- Any domain
Port a dbt macro to each approved warehouse without changing its callers
Part of a dbt project is moving to another warehouse, and a macro its models call only compiles, or only returns correct values, on the old one.
- Transformation
- Any domain
Reconcile equivalent data across two live systems before cutover
A table or model has been rebuilt on another platform or database while the original is still running, and the owner needs evidence the two hold the same data before cutting over.
- Data quality
- Any domain
Move a dbt project to a new destination and check parity before cutover
A dbt project has to run on a different warehouse or lakehouse, and the dashboards and reports that read it cannot show a different number afterwards.
- Transformation
- Any domain