# Before an internal app becomes infrastructure

An editable worksheet from Martin Lepka's marketing data stack journey.

App / workflow:
Owner:
Last reviewed:

1. **Who is it for?** Name the user and the decision this app helps them make.
2. **What does it consume?** List source systems, source owners and expected freshness. Reference the approved credential location; never paste a credential here.
3. **What does it produce?** Describe the record, report or action another person or system depends on.
4. **What can go wrong?** Define a useful check for stale, incomplete, duplicated or wrongly matched data. Specify the expected result and the action when the check fails.
5. **Who operates it?** Name the person who sees failures, owns recovery and covers absences.
6. **When should it move or retire?** State what would justify continued custom ownership, and what evidence would prove a replacement is ready.

## Worked example (illustrative)

A weekly account-priority report helps a marketer choose which accounts to review. Its inputs are CRM account records and dated marketing activity. Its output is a review list with source dates and unresolved matches clearly marked. If the activity source is older than the team's agreed freshness limit, the report shows that limitation and alerts the owner. A replacement is ready when it preserves the agreed population, definitions and history on a checked sample, and its owner has demonstrated recovery from a failed input.

This example is a worksheet illustration, not a claim about a deployed Keboola workflow. Choose checks and freshness limits for your own business decision.