Why account managers need one-pagers and solution briefs
Selling more to an existing customer usually starts with a conversation the account manager is already having. The customer mentions a new team, a new market, or a problem your other product solves, and the account manager wants to send something afterward that explains the offer clearly. Too often, the only thing available is a link to your website, which was written to introduce your company to strangers. It spends its first screen on things the customer already knows and buries the offer they were actually asking about.
A good one-pager fixes that. It is short enough to read between meetings and specific enough to forward to the person who signs off on the budget. A solution brief does the same job for a single problem, such as "reporting across regions" or "onboarding contractors," and has room for a little more detail on how the offer works.
Most teams know they need these and still don't have them, because each one takes real work. Someone has to decide what the offer is for, find the proof, get the pricing right, and write it in a way a busy buyer will read. Then they need a different version for each offer, and ideally a version for the biggest accounts. Marketing teams rarely have the hours, and account managers end up writing their own emails from scratch.
This is work an AI agent handles well, as long as the agent knows your business. It can hold your products, pricing, customer stories, and account history in view at once, and it can write the tenth version as carefully as the first. Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. Here's how it writes one-pagers and solution briefs your account managers will actually send.
How Kite writes sales one-pagers and solution briefs
Kite already knows your business before it writes anything. When your team starts with Kite, it researches your company and saves what it learns to your team's knowledge base, including your positioning, products, pricing, customers, and competitors. That knowledge base is where each one-pager starts.
From there, Kite works out which offer the piece is for and which customers it should reach. With your CRM connected, it reads what each account already has and what your team has discussed with them. Then it gathers the proof that makes the offer believable, writes the master version, and writes shorter versions tailored to specific accounts when your account managers need them.
You review each draft in the conversation, in the Kite web app or in Slack. Once you approve it, Kite delivers it in the format your account managers use, drafts the email that goes with it, and records the send on the account. When pricing or the product changes, Kite updates the one-pagers that mention it.
- Choose one offer and the customers it's for
- Gather the proof that makes the offer believable
- What should a sales one-pager include?
- Write a version for a specific account
- Send it from where your account managers work
- Keep each one-pager current and learn what works
Choose one offer and the customers it's for
Every good one-pager starts with a narrow choice: one offer, one kind of customer, and one problem. A page that tries to explain three add-ons to every customer at once ends up explaining none of them well.
Kite makes that choice from your records. It reads your products and pricing from the knowledge base to define the offer, such as a new analytics add-on or a higher plan with more seats. If you connect HubSpot or Salesforce, Kite reads your existing accounts, their open and closed deals or opportunities, and the notes your team has logged, to see which customers already use the product that leads naturally to this offer.
For example, say you sell scheduling software and you've just launched a payroll add-on. Kite might find 40 customers who run more than 20 hourly staff and have no payroll product in their deal history, and several whose notes mention a payroll headache on a recent call. That tells Kite who the one-pager is for and what problem it should lead with.
Gather the proof that makes the offer believable
A one-pager persuades with specifics, so Kite collects them before it writes. It pulls the facts about the offer from your knowledge base: what it does, how it connects to what the customer already uses, what it costs, and how it's packaged.
Kite also looks for evidence in your customers' own words. It can read the reviews, support threads, and sales-call notes you share, along with public reviews of your product, and sort what it finds into the moments that made people go looking, the problems they described, the objections that almost stopped them, and the results they reported. A line such as "we stopped re-entering hours into a spreadsheet every Friday" makes a better opening than any feature description, because a customer reading it recognizes their own week.
When a claim needs a number, such as hours saved or a result from a case study, Kite uses one you've published or given it. If it doesn't have one, it asks you for it rather than inventing a figure that your account manager would then have to defend on a call.
What should a sales one-pager include?
A sales one-pager should answer the five questions a buyer asks before they agree to another conversation. Kite writes each one-pager around them:
- What problem does this solve for me? The opening names the problem in the customer's terms, ideally tied to something they already do with your product.
- What exactly is the offer? A plain description of what they get, what it connects to, and what changes for them.
- Why should I believe it? A customer result, a short quote, or a concrete example, with the source named.
- What does it cost, and how do I get it? The price or plan, or how pricing works if it depends on their size.
- What happens next? One clear next step, such as a 20-minute walkthrough with their account manager.
For an existing customer, Kite leaves out the general company introduction, since they already chose you once. It uses that space to connect the offer to what they already have.
A solution brief follows the same pattern, focused on one problem or use case. Kite gives it more space to explain how the offer works step by step, who on the customer's team uses it, and what the setup involves, which helps when the buyer needs to explain it to a colleague.
Write a version for a specific account
The master one-pager works for every customer who fits the offer. For your largest accounts, a version written for that one company does better, and Kite can write one whenever an account manager asks.
Kite researches the account before it tailors the page. It reads the company's recent news, such as a funding round, a new office, a leadership change, a product launch, or a burst of hiring in a particular team. It also reads what your team has logged on the account in your CRM, such as which products they use, what came up on recent calls, and when the contract renews. Then it rewrites the opening and the example around that company's situation.
Take the payroll example again. If a customer has just announced that it is opening six new locations, Kite's version for that account opens with what payroll looks like at twelve locations instead of six, and the next step suggests a call before the new sites open.
You can also ask Kite to keep watch on the accounts that matter most. It can follow news about them and tell your team in Slack when something happens that makes an offer timely, along with the account manager's next step.
Send it from where your account managers work
A one-pager only helps when it reaches the customer, so Kite delivers it in the form your account managers will send. It can produce the finished piece as a PDF or a document. If Kite hosts your website, it can also publish the one-pager as a page there, which gives the account manager a link to share and lets Kite see whether people open it.
Kite then drafts the short email that goes with it. The email references the conversation the account manager actually had, links or attaches the one-pager, and proposes the next step. The account manager can send it from their own inbox. If you use Salesforce, Kite can send it from Salesforce once you approve it, logged on the contact's timeline.
Kite also adds a note to the account in HubSpot or Salesforce saying which one-pager went out and why, and it can create a follow-up task for the account owner with a due date. That way the next person who opens the account can see what the customer has already received.
Keep each one-pager current and learn what works
One-pagers go out of date quietly. A price changes, a feature ships, or a case study gets replaced, and the old PDF keeps circulating. Because Kite writes from your knowledge base, it knows which one-pagers mention the thing that changed and can rewrite them for your approval.
Kite also learns from your edits. When you or an account manager changes a draft, such as cutting the pricing line or moving the customer quote higher, Kite records that preference and applies it to the next one-pager.
Over time, Kite can tell you which one-pagers led to something. It reads your HubSpot deals or Salesforce opportunities to see which accounts that received a one-pager went on to open an expansion deal, and, for one-pagers published on a website it hosts, it checks how many people viewed each page. That shows you which offers and angles are worth more of your account managers' time.
What you get
A one-pager for each offer
One page per product, add-on, or plan, written for the customers most likely to buy it, with the problem, the offer, the proof, the price, and the next step.
Solution briefs for the problems that matter most
Longer, problem-focused pieces that explain how an offer works for a specific use case, for buyers who need to explain it to a colleague.
A list of customers who fit each offer
Drawn from your CRM's deals, opportunities, and notes, with the reason each account fits.
Account-specific versions
Tailored one-pagers for your largest accounts, opening with what's happening at that company right now.
A ready-to-send email for each one
A short message the account manager can send, tied to the conversation they actually had.
A record in your CRM
A note on each account saying what was sent and why, plus a follow-up task for the account owner.
How to get started
Start with one offer you want to sell to existing customers. You might ask Kite, "Write a one-pager on our payroll add-on for current customers," or "Our account managers need a solution brief on multi-region reporting."
Kite uses what it already knows about your product and pricing to draft the master version, and it asks for anything it can't confirm, such as a customer result or a pricing detail that isn't on your website. You review the draft in the conversation and tell Kite what to change.
You don't need to connect anything for the first one-pager. Connect HubSpot or Salesforce when you want Kite to find the customers who fit each offer, tailor versions to specific accounts, and record what was sent. Kite asks before it sends any email or publishes a page, so your account managers stay in charge of what reaches their customers.
Integrations used to write sales one-pagers and solution briefs
Kite writes one-pagers from its own knowledge of your business and researches accounts with its built-in data sources. Your CRM tells Kite who your customers are, what they already have, and what your team has discussed with them, and it's where Kite records what was sent.
Find the customers who fit each offer and record what was sent
Kite reads your companies, deals, and the notes, calls, and meetings logged on each account to find customers who fit an offer. After a one-pager goes out, it adds a note to the account and creates a follow-up task for the owner.
Kite reads your accounts, opportunities, and activity history to see which customers could buy more and of what. It can send the account manager's email from Salesforce once you approve it, log it on the contact's timeline, and later read which accounts opened an expansion opportunity.
Common questions
What's the difference between a one-pager and a solution brief?
A one-pager explains an offer, such as a product, an add-on, or a plan, in a single page meant to start a conversation. A solution brief explains how you solve one specific problem or serve one use case, and it usually runs one to two pages because it includes more about how the solution works and who uses it. Many teams use the one-pager to get a meeting and the solution brief to help the buyer make the case to their colleagues. Kite writes both, and it can write a solution brief for each of the use cases your customers buy for.
Can Kite design the one-pager, or does it only write it?
Kite writes the content and delivers it as a clean, readable PDF or document, or as a page on a website it hosts. If your team has a designed, branded template for sales collateral, give Kite's copy to whoever maintains that template, or paste it in yourself. Tell Kite how much space each section of your template allows, and it writes the copy to fit.
Where can I see examples of sales one-pagers?
One-pager examples: real sales one-pagers and solution briefs, and how to make one Coming soon collects real examples and explains what each one does well.
Can Kite write one-pagers for new prospects, not just existing customers?
Yes. The work is the same, but the content changes. A one-pager for a prospect needs a short introduction to your company and more proof, because the reader hasn't used your product yet. Kite adjusts the opening and the evidence to the reader, and it can tailor a version to a target account using the same research on the company's recent news and hiring.
Can Kite write other sales collateral for account managers?
Yes. Beyond one-pagers and solution briefs, Kite writes battle cards and objection handling for your sales team, company briefs that prepare an account manager for a call, and the follow-up emails that go out afterward. All of it draws on the same knowledge of your products, pricing, customers, and competitors, so the collateral tells one consistent story.