Purpose & Intention — Unit 14, Upper-intermediate English
Collocations for stating why something is done — goals, design intent, and planned outcomes.
Reading: Product Brief — Self-Serve Portal
**Product brief excerpt · Self-Serve Portal · v2.1**
The portal **is designed to** reduce tier-one support tickets and **is aimed at** mid-market administrators who manage billing without a dedicated account team. We paused public billing **in order to** complete UAT and validate rollback paths. Contractors were hired **with a view to** accelerating QA during the final sprint.
Single sign-on **facilitates** faster onboarding and **enables** partner integrations through scoped API keys. Rate limits **prevent** API abuse during traffic spikes. The approval workflow **was intended to** limit data exposure; audit logs were retained **so as to** support external reviews.
Training modules **are geared towards** new customer-success leads who will coach pilot accounts. The dashboard **serves to** highlight regional risk and usage anomalies. **The underlying rationale** **is** faster time-to-value without adding headcount.
We redesigned onboarding **with the aim of** reducing churn in week two. Data fields **are collected for the purpose of** fraud prevention and licence reconciliation. Teams worked **in pursuit of** a zero-downtime release and **are working toward** SOC 2 certification this year.
The API release **paved the way for** partner integrations planned in Q1. We delayed launch **in the interests of** stability after two critical defects surfaced. **We set out to** cut support tickets by thirty percent; **the end goal** **is** zero-touch provisioning for standard plans. The next steering review is scheduled for the first week of October.
**Section 7 — Non-goals**
This brief has so far described what the portal **is intended to** do. The following states what it is not for, and these exclusions are as binding on the roadmap as the goals above.
**The portal is not intended to serve enterprise administrators.** Enterprise accounts have named support and negotiated terms, and every attempt to accommodate both audiences in one interface has produced a portal that serves neither. Where an enterprise requirement conflicts with a mid-market one, the mid-market requirement wins by default, and the conflict should be escalated rather than compromised.
**It is not designed to replace the support team.** The thirty-percent ticket target refers to tier-one volume. Tier-two and tier-three volume is expected to remain flat or rise slightly, since deflecting simple questions raises the average complexity of what remains. **Any plan predicated on** reducing total support headcount misreads this brief.
**It is not a reporting tool.** Requests for exportable analytics have been declined four times. The dashboard exists **so as to** surface anomalies requiring action, not to answer arbitrary questions. A component that must answer arbitrary questions is a different product with a different cost.
**It is not a route to SOC 2.** Certification work runs in parallel and shares two engineers; it does not share a deadline. Coupling them, as the March plan did, meant a slip in either delayed both.
**One deliberate omission.** We have not built self-serve cancellation, and this was a decision rather than an oversight. **The rationale is** that cancellation in this segment is frequently reversible with a conversation, and the data supports this: of 212 cancellation requests handled by an agent last year, 74 were retained. We accept that this is friction the customer did not ask for, and we will revisit it at the twelve-month review with retention data rather than principle.
Vocabulary from this unit
| Frame | Example |
|---|---|
| in order to | Paused in order to fix defects. |
| with a view to | Hired with a view to scaling support. |
| so as to | Archived logs so as to meet retention. |
| aimed at / geared towards | Aimed at reducing churn. |
| designed to / intended to | Designed to automate approvals. |
| Verb | Example |
|---|---|
| facilitate | Facilitates cross-team planning. |
| enable | Enables real-time reporting. |
| prevent from | Prevents duplicate charges. |
| end goal | End goal: self-serve provisioning. |
| Phrase | Example |
|---|---|
| with the intention of | We paused rollout with the intention of fixing defects. |
| for the purpose of | Data are collected for the purpose of fraud prevention. |
| in pursuit of | Teams worked in pursuit of a zero-downtime release. |
| serve to | The dashboard serves to highlight regional risk. |
| act as a catalyst for | The audit acted as a catalyst for process reform. |
| be geared toward | The pilot is geared toward enterprise buyers. |
| work toward | We are working toward SOC 2 certification. |
| with the aim of | We redesigned onboarding with the aim of reducing churn. |
| pave the way for | The API release paved the way for partner integrations. |
| in the interests of | We delayed launch in the interests of stability. |
| set out to | We set out to cut support tickets by thirty percent. |
| underlying rationale | The underlying rationale is faster time-to-value. |
This is the free sample from this unit. The full unit adds 1 more reading passage, comprehension questions with an answer key, the listening exercises, flashcards for the vocabulary above, and a speaking task — with your progress tracked so the next unit unlocks when you are ready for it.
Common questions
What level is this unit?
Upper-intermediate — roughly CEFR B2. If you are not sure of your level, the course places you with a short diagnostic before you start rather than making you guess.
Do I need to pay to use this?
The reading passage and vocabulary on this page are free to read. The rest of the unit — the remaining passages, the exercises, the listening, the answer key and the progress tracking — is part of the paid General English course.
Is this British or American English?
British English spelling and vocabulary, which is what most learners in Azerbaijan are taught and what IELTS expects, though both are accepted in the exam.