Understand projects, products and budgets
Project vocabulary helps decide who does what, with which outcome and verification. Separate need, proposed solution and approval responsibility. A budget or deadline makes sense only with explicit scope and dependencies.
38 concepts to explore with their definitions and practical advice.
Search the full glossary
A reading path
1. Define the outcome
Describe audience, problem and expected deliverable. A blocking requirement should be distinguishable from a preference or option.
2. Compare approaches
Examine required functions, data to maintain and exit conditions. A minimum version tests a hypothesis without hiding journey limitations.
3. Track decisions
Identify expected inputs, enquiry owner and approval points. Scope changes should be resolved before retaining the same commitments.
Useful distinctions
Acceptance criteria / SLA
Acceptance criteria describe a deliverable outcome and the test accepting it. An SLA defines service-level commitments within a context. They concern different situations and periods.
Starting price / Exit cost
A starting price does not describe every option or upkeep. Exit cost concerns recovery and transfer of data or service. Compare equivalent scope before drawing conclusions.
Use the vocabulary to make a decision
Situation
Two proposals look different while answering the same brief.
Before deciding
Compare deliverables, responsibilities, migrated data, upkeep and included tests. Price differences can reflect different scope.
A concrete check
Ask a specific question about each non-comparable item and retain the answer with the proposal.
All concepts in this topic
Links open the full definition on its alphabet page. Acronyms and synonyms remain searchable from the main glossary.
- Acceptance criteria
- AI readiness
- Automation
- B2B
- B2C
- Benchmark
- Booking capacity
- Booking slot
- Checkout journey
- Comparable criterion
- CRM
- Double booking
- E-commerce
- Enquiry acknowledgement
- Enquiry owner
- Exceptional opening hours
- Exit cost
- Hard requirement
- Kanban
- Magento
- Migration
- MVP
- Prelaunch checklist
- Price effective date
- Product availability
- Product difference
- Product page
- Product variant
- QA
- Response time commitment
- ROI
- SLA
- Starting price
- Vacancy status
- Web sustainability
- Website brief
- Website job opening
- Yield management
Frequently asked questions
Must the whole project be detailed before the first discussion?
Present need, existing site, deadline and known constraints. Uncertain items can become questions to resolve rather than implied commitments.
Does checking a task accept the deliverable?
Performing a task and accepting its result are distinct. Check the agreed criterion with intended data and context, then record remaining limitations.
Primary reference documents
These documents explain the technical concepts. The reading paths and decision examples are editorial methods to adapt to your project.