How to Build a Free Trial Landing Page That Actually Converts — A Complete Direct Response Breakdown
“Most SaaS landing pages fail for the same reason: they describe the product instead of selling the outcome. This is a full case study of how we built a high-converting free trial landing page for StreamlinePro — a B2B project management tool for marketing agencies — from blank brief to final HTML, using direct response principles at every decision.”
What Direct Response Actually Means — And Why Most SaaS Pages Ignore It
Direct response copywriting is often described as "copy that gets people to act now." That definition is technically correct and practically useless. It tells you the goal but nothing about the method.
Here is a more useful definition: direct response copy is writing that treats every sentence as a conversion variable. Not decoration. Not brand voice for its own sake. Every word is accountable to one question — does this move the reader one step closer to clicking the button?
Brand copy can afford to be impressionistic. It builds associations over time, across campaigns, in aggregate. Direct response copy does not have that luxury. A landing page is a single session, a single reader, a single decision. Either they sign up or they leave. That asymmetry changes everything about how you write.
Most SaaS landing pages fail because they are written by product teams or brand marketers who have never internalised that distinction. The result is pages that are technically accurate, visually polished, and utterly unconvincing. They explain the product. They do not sell the outcome. They list features. They do not address fear. They use the company's language, not the customer's language. And they wonder why the conversion rate is 2%.
The StreamlinePro brief is a clean test case. The product is a project management platform for marketing agencies — a crowded category dominated by ClickUp, Asana, and Monday.com. There is no moat. There is no brand recognition. The only lever is the quality of the argument made on the page. That is a pure direct response challenge, and it is what this breakdown examines.
“The page is not a brochure. It is a conversation — with a stranger who does not trust you yet, who is tired of being sold to, and who will close the tab in eight seconds if you do not immediately convince them you understand their specific problem.”
Starting Point: Reading the Brief Like a Strategist, Not a Copywriter
The brief names the product, the target audience, the pain points, and the conversion goal. Most copywriters read a brief and immediately start drafting headlines. That is the wrong instinct. The right instinct is to interrogate the brief before writing a single word.
The brief tells us the target audience includes Marketing Managers, Project Managers, Account Executives, Creative Directors, and Team Leads at marketing agencies. That is five different roles. The instinct is to write copy that covers all five. The correct instinct is to identify which one experiences the pain most acutely and make them the primary reader.
In an agency, the person who loses sleep over missed deadlines, client complaints, and team chaos is the Project Manager or the Account Executive — not the Creative Director, who is downstream of the problem, and not the Team Lead, who is insulated from client pressure. The Project Manager is the one who gets the 9pm email from the client asking why the brief is late. They are the reader the hero section is written for.
The brief also tells us the pain points: disorganised projects, missed deadlines, poor communication, lack of visibility, inefficient workflows. These are generic enough to describe every project management tool that has ever existed. The challenge is to make them specific enough to feel personal. Generic pain points create generic copy. Specific pain points create recognition — the reader nods, leans forward, and keeps reading.
Translating Brief Pain Points Into Real Language
Here is how the pain points in the brief were translated into specific, language the target reader actually uses:
From Generic Pain Points to Specific Scenes
How abstract brief language was rewritten into copy that produces recognition, not just comprehension.
| Brief language | What it actually means | Copy used on the page |
|---|---|---|
| Disorganised projects | Work scattered across Slack, email, spreadsheets, sticky notes — no single source of truth | "Scattered spreadsheets, missed campaign deadlines, and endless status emails" |
| Missed deadlines | Nobody knows a deadline is at risk until it has already been missed. The PM finds out from the client. | "Deadline visibility only exists in one person's head — until it's too late" |
| Poor communication | Clients email for status updates. The PM has to chase five team members to compile an answer. | "Clients chasing status updates via email every other day" |
| Lack of visibility | Monday morning is spent rebuilding a picture of where everything stands, instead of acting on it. | "Hours each Monday rebuilding reports from five different tools" |
| Inefficient workflows | Every new client project starts from scratch, even though 80% of it is the same as last time. | "Onboarding new clients starts from scratch every single time" |
The pattern is consistent: take the abstract noun from the brief and replace it with a specific scene. Not "communication breakdown" but "clients chasing status updates via email every other day." The reader does not recognise "communication breakdown." They recognise the 4pm email from the client that starts with "Just checking in…"
“The shift from brief language to specific scenes is not just stylistic. It is strategic. Generic pain points trigger no emotional response because they require the reader to do interpretive work — to translate the abstract into their own experience. Specific scenes do that work for them. Recognition is instant and the connection is made before the conscious mind can object.”
The Wireframe: Architecture Is Argument
Most people treat a wireframe as a layout exercise. It is not. A wireframe is a persuasion plan. The sequence of sections is the sequence of the argument, and the sequence of the argument determines whether the reader reaches the CTA or leaves mid-page.
Before drawing a single box, the question to answer is: what does this reader need to believe before they will give us their email address? In this case, the answer breaks down into four beliefs:
This product is for me specifically. Not for IT teams. Not for construction companies. For marketing agencies doing exactly the kind of work I do.
Other people like me use it and think it works. I am not taking a risk on something unproven.
It actually does what it says. I can see what the product looks like and it is not just marketing language.
The trial is genuinely free and low-risk. I do not have to give my credit card. I can cancel. There is no catch.
Every section of the wireframe was designed to build one of these beliefs, in the order they need to be built. The hero builds belief one. The ratings row and product screenshot build beliefs two and three. The old-way-vs-new-way and features section reinforce beliefs one and three. The trial details section, placed last, handles belief four — because explaining the trial mechanics too early creates friction before the reader cares.
The Two-CTA Structure
One of the most consistently misunderstood elements of landing page architecture is CTA placement. Conventional wisdom says "put the CTA above the fold." That advice is half-right and half-dangerous.
Yes, put a CTA above the fold — for the reader who lands on the page already sold. They came from a warm referral, a strong ad, or a competitor comparison. They do not need to be convinced. They need to act. The hero CTA captures them.
But most readers are not pre-sold. They need to be walked through the argument. A reader who scrolls through the full page — who reads the old-way-vs-new-way, explores the features, reads the testimonials — is a significantly warmer lead than the hero-CTA skimmer. The second CTA, at the bottom, in the dark trial details section, captures that reader at exactly the moment they have been fully persuaded.
The sticky navigation CTA is the third layer — always visible, always one click away, for readers who reach their point of persuasion somewhere in the middle.
Wireframe Flow Logic
Land → Hero CTA (pre-sold reader) → Scroll → Ratings (credibility) → Screenshot (prove it's real) → Logos (social proof) → Old vs. New (address objections) → Features (explain what it does) → Metrics + Testimonials (prove it works) → Final CTA (fully convinced reader)
The sticky nav CTA intercepts the reader at any point where they reach spontaneous persuasion.
Writing the Hero: The Most Expensive Real Estate on the Internet
The hero section — the first thing the reader sees before scrolling — is where most landing pages win or lose their conversion. Research consistently shows that the majority of bounce decisions happen within the first few seconds of page load. In practice, that means the headline, the subheadline, and the CTA button together need to accomplish three things simultaneously: confirm the product category, identify the target audience, and communicate a distinct benefit worth exploring further.
This is what was written for StreamlinePro:
Hero Copy
Eyebrow: 🚀 Trusted by 2,400+ marketing agencies
H1: The project management platform built for marketing agencies
Subheadline: Replace scattered spreadsheets, missed campaign deadlines, and endless status emails with one organized workspace your whole team will actually use.
CTA button: Start Free Trial
Microcopy: ✓ Free for 14 days ✓ No credit card required ✓ Cancel anytime
Dissecting the Headline Decision
The headline "The project management platform built for marketing agencies" is deliberately not clever. It does not use a pun, a provocative question, or an abstract promise. It uses direct category language ("project management platform") and a targeting qualifier ("built for marketing agencies").
This is intentional. Clever headlines require cognitive effort. They are appropriate in contexts where the reader has already committed attention — a long-form article, an email they chose to open. They are high-risk on a landing page, where the reader is evaluating whether this page deserves their attention at all. A clever headline that requires two seconds to parse has already lost the reader who was on the edge.
The phrase "built for" is doing more work than it appears to. "Made for" is inert. "Designed for" is corporate. "Built for" has a craft implication — it suggests intentional engineering, not after-the-fact adaptation. It draws a direct contrast with ClickUp and Asana, which are general-purpose tools that agencies can adapt to their needs. StreamlinePro was built for this specific audience. That distinction matters to an agency PM who has spent two years fighting a generic tool's interface to make it work for campaign management.
The Subheadline: Three Pains, One Solution, One Objection Neutralised
The subheadline follows a precise structure that is worth examining line by line: "Replace scattered spreadsheets, missed campaign deadlines, and endless status emails with one organized workspace your whole team will actually use."
Three pain points are named — not described, named. "Scattered spreadsheets." "Missed campaign deadlines." "Endless status emails." Each one is a three-word scene that any agency PM will have lived through this week. The reader does not need to interpret them. They are recognised immediately.
The solution is "one organized workspace" — singular, simple, not technical. It does not say "centralised project management infrastructure." It says one workspace. That is a benefit written in human language.
The last five words — "your whole team will actually use" — are the most important words in the subheadline. They address an objection that every agency PM carries from past experience: we bought a tool before, we set it up, and the team stopped using it after three weeks. "Actually use" acknowledges that objection without a defensive disclaimer. It flips the memory of past failure into a reason to try again.
“Technique: Pre-emptive objection handling
Naming an objection before the reader consciously raises it defuses it. When copy says “actually use,” the reader’s instinct is not “is that true?” but “yes, that’s what I need.” The objection is acknowledged, validated, and neutralised in two words. This is more efficient than a paragraph of reassurance after the fact.”
The Eyebrow Tag and Social Proof Placement
The eyebrow tag — "Trusted by 2,400+ marketing agencies" — sits above the headline, not below the CTA. This is a deliberate structural choice. The reader encounters social proof before they read the product claim. This primes them to evaluate the claim as something already validated by peers, not as something they need to verify from scratch.
The number 2,400 is specific and non-round. "Thousands of agencies" registers as marketing language. "2,400+" registers as a real count someone has taken the trouble to measure. Specificity signals honesty. The mind's default assumption is that a specific number is accurate; the assumption for round numbers is that they are approximations.
The Old Way vs. New Way: The Most Underused Section in SaaS Copy
The before-and-after contrast section is one of the most powerful tools in direct response, and one of the most poorly executed in SaaS. Most companies write it as a feature comparison. That is the wrong frame entirely.
A feature comparison answers the question "what does the product do?" A before-and-after section answers a different question: "what does my life look like without this product?" The second question is emotionally active. The first is intellectually passive. Emotionally active questions drive decisions. Passive questions drive research.
Here is how each contrast pair was constructed for StreamlinePro, and the reasoning behind each:
"Projects spread across Slack, email threads, spreadsheets, and sticky notes" vs. "Every campaign, task, file, and conversation in one organized workspace." — The left side names four specific tools. Not "fragmented systems." Slack. Email. Spreadsheets. Sticky notes. The reader's own setup is described back to them.
"Deadline visibility only exists in one person's head — until it's too late" vs. "Automated deadline alerts before anything slips — agency-wide visibility." — The phrase "until it's too late" is doing the work. It activates memory of the specific moment the PM found out about a missed deadline from the client, not from their own system.
"Clients chasing status updates via email every other day" vs. "Client-facing live status pages shareable with a single link." — The left side captures a specific irritation that erodes client relationships. The right side offers a concrete mechanism, not just an outcome.
"Hours each Monday rebuilding reports from five different tools" vs. "Real-time dashboards ready instantly — reclaim 6 hours a week." — Monday morning is named specifically because that is when it happens. The metric (6 hours) in the right column directly responds to the time cost named on the left.
"Onboarding new clients starts from scratch every single time" vs. "30+ agency-built campaign templates — launch new projects in minutes." — "Every single time" is emphasis, but it is also accurate. The reader who has done this knows the exact amount of wasted setup work it describes.
"No visibility into team capacity — best people burn out silently" vs. "Workload views across every team member — balance capacity with confidence." — "Burn out silently" is the emotional spike in this pair. It captures the delayed-discovery problem: the PM does not know someone is overloaded until they resign or miss a deadline.
“The before column is not a feature list in reverse. It is a hall of mirrors — designed to show the reader their own current reality, in language specific enough to produce recognition, not just comprehension.”
Writing Features Without Sounding Like a Product Manual
Feature sections are where direct response discipline is most frequently abandoned. The instinct is to describe what the product does. The correct instinct is to describe what the product does in the context of what the reader is trying to accomplish.
There is a useful formula here: [Feature name] + [mechanism] + [outcome the reader cares about]. Not "Kanban boards." But "Drag-and-drop Kanban boards for campaign workflows" — which tells you what it is, how it works, and why it matters to an agency specifically.
The tab structure for StreamlinePro's features section was chosen over a traditional 2x2 grid for a specific reason. On a landing page, a grid layout forces all features to compete for attention simultaneously. A tabbed layout allows each feature to make its case fully — copy, benefit bullets, and a live UI visual — before the reader moves to the next. The reader controls the pace. The feature gets its complete argument made.
Headline Choices for Each Feature Tab
Each feature tab headline follows a specific pattern. It does not use the feature name as the headline. It uses the outcome the feature delivers:
Task Management tab: "Kanban, List, or Calendar — your team's choice." The value is flexibility and team adoption, not the feature itself.
Campaign Timelines tab: "See every campaign deadline at a glance." Not "Gantt charts." The outcome is visibility, and the word "glance" signals that achieving it is effortless.
Live Dashboards tab: "Real-time visibility across every client project." The qualifier "every client project" matters for an agency managing multiple accounts simultaneously.
Team Collaboration tab: "Context that lives with the work — not in a Slack thread." This headline directly names the alternative the reader currently uses and positions it as inferior without attacking it.
The last headline is worth dwelling on. "Context that lives with the work — not in a Slack thread" works because it is specific about the enemy. Not "better communication." Not "centralized context." The reader knows exactly what a Slack thread is: six months of project decisions buried in a channel no one can search effectively. Naming it creates instant contrast without requiring explanation.
Social Proof: How to Make Fake Testimonials That Read Like Real Ones
The brief specifies that testimonials are illustrative — meaning fabricated for the purposes of the exercise. That creates an interesting challenge: how do you write fake testimonials that have the texture of real ones? The answer reveals what makes real testimonials persuasive in the first place.
Weak testimonials follow this template: "Great product! Has really improved our workflow. Highly recommend." This is worthless as social proof because it lacks specificity. The reader cannot tell whether this testimonial came from a real person with a real problem or from the marketing team. It reads like a product review on an e-commerce site, not like a peer recommendation.
Strong testimonials contain three elements:
A specific problem or situation before the product. Not "we were struggling" but "we lost a client over a missed deliverable we didn't even know was at risk."
A specific timeline or mechanism of change. Not "things improved" but "within two weeks of switching."
A specific measurable outcome. Not "better results" but "we haven't missed a single deadline in eight months."
The featured testimonial for StreamlinePro reads: "Before StreamlinePro, we lost a client over a missed deliverable we didn't even know was at risk. Within two weeks of switching, we had full visibility across every active project. We haven't missed a single deadline in eight months." Every element is present. The problem is specific and emotionally significant (losing a client). The timeline is specific (two weeks). The outcome is specific and measurable (eight months, zero missed deadlines).
The attribution matters too. "Jamie Kowalski, Creative Director, Meridian Creative Agency" is the full structure. Job title places the reviewer in the right audience. Agency name makes the reviewer feel like a real business, not an anonymous username. Even the name choice matters — a plausible but uncommon name reads as more credible than John Smith or Alex Johnson, which read as composites.
The Metrics Strip: Numbers That Earn Their Place
The three metrics used — 3×, 94%, 6hrs — each follow a principle: they are meaningful to the reader's specific pain points, and they are accompanied by context that prevents misreading.
"3× faster project setup with pre-built agency campaign templates" is better than "3× faster onboarding" because it names the mechanism. The reader understands why: it is the templates. They can connect the number to the feature. A decontextualised multiplier is unverifiable and therefore unconvincing.
"94% of teams report fewer missed campaign deadlines within the first month" uses a qualifying phrase — "within the first month" — that simultaneously adds credibility (it is specific) and urgency (the payoff is fast).
"6 hrs saved per team per week — reclaimed from manual status reporting" mirrors the pain point from the old-way-vs-new-way section. The reader who read "hours each Monday rebuilding reports from five different tools" and felt recognition will see "6 hrs saved per team per week" and do the calculation themselves. That active engagement is more persuasive than any claim the copy can make.
The Final CTA: Closing Arguments in the Courtroom
By the time the reader reaches the final CTA section, they have read everything. They know what the product does, they have seen social proof, they have seen the metrics. The job of the final CTA section is not to introduce new information. It is to remove the last remaining reason not to act.
For a free trial CTA, the last remaining reason not to act is almost always risk. Not cost — the trial is free. Not effort — the signup form is one field. The risk is the risk of commitment. Starting a trial, even a free one, triggers a psychological investment. The reader anticipates the possibility of being upsold, nagged by email, or trapped in a cancellation process. The final CTA section exists to neutralise each of these fears explicitly.
“Final CTA Copy
H2: Start delivering projects on time. Every time.
Subheadline: Free for 14 days. No credit card. Setup in under 30 minutes.
Trust line (below form): ✓ Free 14 days · ✓ No credit card · ✓ Full access · ✓ Cancel anytime”
The H2 "Start delivering projects on time. Every time." is the only place in the entire page that steps back from pain points and promises a clean outcome. The reader has spent the page having their current pain validated. The final headline offers the destination: not "try our software" but "deliver projects on time, every time." That is what the reader actually wants. The software is the mechanism. The outcome is the sale.
"Setup in under 30 minutes" in the subheadline addresses the hidden fear of implementation: not that the trial will be expensive, but that getting started will be complicated, that it will require a two-hour onboarding call or a week of data migration. Thirty minutes is below the threshold of "this will disrupt my week." It makes the decision feel small, even if the impact is large.
The One-Field Form: Why Less Is More At This Specific Moment
The sign-up form contains one field: work email. No name. No company. No role. No phone number. This is a deliberate decision, and it goes against the instincts of most sales teams, who want to collect as much data as possible at the point of first contact.
Here is the logic. The reader who has reached the final CTA is persuaded. Any friction introduced at this moment — any additional field, any required field beyond email — is a leak in a conversion that was already won. The goal at this stage is not data collection. The goal is completing the action before the reader changes their mind.
Everything else — first name, last name, agency name, role, team size — is collected in the onboarding flow, after the account is created. At that stage, the user is invested. They have taken the action. They are inside the product. They will answer five questions because they want the product configured to their situation. Asking those same questions on the landing page, before the value has been experienced, adds friction to a decision that has not yet been made.
SEO as a Conversion Discipline, Not Just a Traffic Discipline
Most discussions of SEO for landing pages treat it as separate from conversion — first get the traffic, then convert it. That is the wrong mental model. For a page like StreamlinePro's free trial page, keyword strategy and conversion strategy are the same strategy, because the search query that brings the reader to the page tells you exactly where they are in the buying process.
A reader who arrives from the query "project management free trial no credit card" is already sold on the concept of a free trial. They are at the bottom of the funnel. They need one thing: confirmation that this product is for people like them. The hero section handles that in four seconds. The conversion window is wide open from the moment they land.
A reader who arrives from "project management software marketing agencies" is earlier in their journey. They are evaluating whether this category of solution applies to their situation. For them, the old-way-vs-new-way section — which mirrors their daily problems back to them — is the primary conversion driver. They need to see themselves in the page before they will consider the trial.
This is why the keyword strategy was built outward from niche, high-intent terms rather than starting with broad head terms. "Project management software" has enormous search volume and keyword difficulty above 85 — meaning ClickUp, Asana, and Monday.com own the first page and will continue to own it for years. "Project management software for marketing agencies" is achievable in 6-12 months with strong on-page SEO and a modest backlink strategy. The traffic volume is lower, but the conversion rate is substantially higher because the reader's intent exactly matches the page's offer.
Meta Title and Description as Direct Response Copy
The meta title and description are the first copy the reader sees — before they even reach the page. They appear in the search results, and they are a direct response copywriting challenge in their own right: you have one line to outperform nine other results for a reader with a specific intent.
“Final Meta Copy
Title: StreamlinePro — Free 14-Day Trial | Project Management for Marketing Agencies
Description: StreamlinePro is the project management platform built for marketing agencies — track every campaign deadline, keep clients impressed, and reclaim hours lost to manual reporting. Start your free 14-day trial. No credit card required.”
The title front-loads the brand name, follows immediately with "Free 14-Day Trial" — the conversion signal — and qualifies the audience with "for Marketing Agencies." The structure is brand → offer → category → audience. The reader evaluates these in order and self-selects within three seconds. A marketing agency PM sees their profession named in a SERP listing and their click probability increases significantly.
The meta description follows the AIDA model — not because it is a framework to apply mechanically, but because the sequence it describes is the sequence of persuasion: product named and positioned (attention) → three specific outcomes named (interest) → clear CTA (desire) → risk removed (action). "No credit card required" closing the description is the single highest-impact trust phrase in SaaS copy and belongs at the end, not the beginning — the hook and the benefits land first, the trust signal closes.
What This Page Gets Right — And Where the Real Risks Are
A comprehensive breakdown of this kind would be dishonest if it did not examine the assumptions the page is built on and where those assumptions create risk.
What Works
The specificity of language throughout. The old-way-vs-new-way section. The single-field form. The two-CTA architecture. The niche SEO targeting strategy. These are not defaults or best guesses — they are deliberate decisions grounded in direct response principles and in the specific context of this audience.
The page also handles the competitive context well. It does not attempt to compete with ClickUp on feature breadth. It does not claim to be "better" in abstract terms. It positions specifically — built for marketing agencies — and lets the audience qualifier do the differentiation work. A marketing agency PM reading this page does not need to be told it is better than ClickUp. They need to be told it is for them, specifically. That is a more defensible claim and a more persuasive one.
The Assumptions That Need Testing
Several assumptions in this page are directionally strong but empirically unverified:
The primary reader assumption. The page is written primarily for the Project Manager persona. If the actual buyer is more often the Agency Owner or Creative Director, the pain points hierarchy needs reordering. This is testable with even a small number of customer interviews.
The headline approach. The direct, non-clever headline is the right call for a cold-traffic page, but if a significant portion of traffic arrives from warm referrals or existing community engagement, a more aspirational headline may outperform. A/B test is straightforward.
The tab structure for features. Tabs hide content, which reduces engagement for readers who do not interact with them. The wireframe note acknowledges this trade-off. For a page driving paid traffic to an audience that is already feature-aware, a scrollable grid may outperform. For a page educating a cold audience, tabs reduce overwhelm and may perform better. This needs traffic source data to decide definitively.
The metrics. 3×, 94%, 6 hours are illustrative numbers. If the real product metrics are less dramatic, using inflated numbers in a prototype that becomes a live page is a direct trust problem. Every metric on a live page needs a defensible source — whether from customer research, actual product data, or third-party benchmarks.
The Principles Behind the Page
The StreamlinePro landing page is not a template. It is the output of a set of principles applied to a specific brief, a specific product, and a specific audience. Understanding those principles is more valuable than copying the structure, because the structure is only correct in this context.
The underlying principles are consistent across direct response work:
Specificity outperforms generality every time. Specific pain points, specific names, specific numbers, specific timelines. Generality requires the reader to do interpretive work. Specificity does it for them.
Sequence is argument. The order of sections is the order of the persuasion. Every section earns the right to the next. If a reader would find section five unconvincing without having read section three, that is a structural problem, not a copy problem.
Objections must be named before they are handled. An objection the reader raises themselves, mid-read, is persuasion-breaking. An objection named by the copy — "your whole team will actually use" — is neutralised before it can form.
Every friction point is a conversion leak. The one-field form is not minimalism for its own sake. It is the recognition that every additional field is a gate between the reader and the action, and every unnecessary gate loses a percentage of the conversions that were already won.
SEO and conversion are not separate disciplines. The keyword strategy determines who lands on the page. The copy determines whether they convert. When the keyword intent and the page argument are aligned — when the reader who searched "project management free trial no credit card" lands on a page that immediately offers exactly that — the gap between traffic and conversion closes.
The assignment brief asked for a wireframe, core content, and basic meta details. What it actually required — and what any direct response challenge requires — was a fully integrated argument: every structural decision connected to a persuasion purpose, every line of copy connected to a specific reader belief, every SEO decision connected to the intent of the specific buyer being targeted.
That is what direct response copywriting is. Not clever writing. Not persuasive writing in the abstract. An argument, built piece by piece, designed for a specific reader, at a specific stage of a specific decision. When the argument is complete, the CTA is not a request. It is the logical next step.
“This breakdown was built using the complete StreamlinePro brief, wireframe, core content document, and SEO/metadata specification produced for the test assignment. Every copy decision referenced is from the live deliverable, annotated here with its direct response rationale.”
