What the Backend Actually Does
The backend receives requests, applies business and permission rules, coordinates data and external services, and returns controlled results. Identify which product rules must be enforced centrally even when a client or integration sends an unexpected request.
What You Will Be Able to Decide
- Explain what the backend actually does in product and business terms.
- Apply this decision: Identify which product rules must be enforced centrally even when a client or integration sends an unexpected request.
- Recognise this material risk: the product appears correct through its interface while direct requests bypass important rules.
- Ask a consultant for evidence rather than reassurance.
A founder is reviewing how the product will enforce rules and respond when a request does not go to plan.
The backend receives requests, applies business and permission rules, coordinates data and external services, and returns controlled results.
A consultant can recommend and implement the technical approach. The founder still needs to decide which outcome matters, which risk is acceptable, and what evidence is sufficient.
The Founder Situation
A founder is reviewing how the product will enforce rules and respond when a request does not go to plan.
The immediate question is what the backend actually does. The technical label matters only because it changes a product decision, a responsibility, or the evidence required before launch.
Technical term
What the Backend Actually Does
The backend receives requests, applies business and permission rules, coordinates data and external services, and returns controlled results.
Treat it like a clause in a commercial agreement: its value comes from making expectations and consequences clear, not from sounding formal.
What Matters in Practice
Start with the product consequence, then choose the simplest technical treatment that protects it. A longer tool list is not a stronger plan.
For this decision, the useful standard is that important rules hold for valid, invalid, repeated, and unauthorised requests.
- Make the decision explicit: Identify which product rules must be enforced centrally even when a client or integration sends an unexpected request.
- Ask what evidence would show that the chosen approach works.
- Name the person or provider responsible when the approach fails.
- Record the result in the backend proposal and operational acceptance criteria.
A Proportionate Decision
Identify which product rules must be enforced centrally even when a client or integration sends an unexpected request.
The principal risk is that the product appears correct through its interface while direct requests bypass important rules. This does not require the most expensive possible solution. It requires the consequence to be understood and the control to match it.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
Strong Evidence and Weak Reassurance
Warning Signs
- Nobody can explain how what the backend actually does changes a user or business outcome.
- The proposal does not address this risk: the product appears correct through its interface while direct requests bypass important rules.
- The only evidence is a successful demonstration of the easiest path.
- The decision has no named owner, boundary, or review point.
- A provider-specific feature is being mistaken for a permanent product requirement.
Questions to Ask a Consultant
- What decision are we making about what the backend actually does?
- Which user or business outcome does the recommendation protect?
- How have we reduced or accepted this risk: the product appears correct through its interface while direct requests bypass important rules.
- What evidence can I review without relying on the original implementer?
- What is deliberately deferred, and when will it be reconsidered?
- Who owns the accounts, data, documentation, and recovery process?
Key takeaway
Key Takeaway
The backend receives requests, applies business and permission rules, coordinates data and external services, and returns controlled results. The founder's job is to make the consequence explicit; the consultant's job is to recommend and demonstrate a proportionate implementation.