Product positioning, launch copy and coordinated creative work supported early adoption and the active-user benchmarks tied to growth funding.
Skip to content
Business & digital growth · Selected project 72
The Sale Was Signed. The Customer Still Had to Get Started
Onboarding messages, instructional scripts and portal requirements reduced early friction and improved first-90-day retention.
My role
Communications Architect & Journey Planner
Project context
Seattle & Bellevue, WA (Tech Operations & SaaS)
Signing the agreement is an important moment for the seller. For the customer, it may be the beginning of a new set of questions. What happens first? Who does what? How much of the original promise will make sense once real people begin using the service?
I worked as communications architect and journey planner on this high-value SaaS onboarding assignment. I mapped the client journey, wrote instructional-video scripts and prepared user-experience briefs for the portal developers. The project reduced early friction and improved retention over the first 90 days.
The customer needed a sequence
An organization can provide a great deal of onboarding information without providing a clear order in which to use it. A document library is not automatically a beginning. The new customer needs to understand what deserves attention now and what can wait.
The journey work addressed that progression. My role was to connect the customer's questions with the communication and portal experience. The objective was to make the early relationship easier to navigate, so that the service could begin demonstrating the value described during the sale.
Instructional writing is a form of hospitality
A useful instruction anticipates the reader's situation. It explains the next action at the right level, without assuming that unfamiliar terminology or a missing step will somehow become obvious. Video does not remove that responsibility; it adds decisions about pace, sequence and emphasis.
I wrote the instructional scripts around the intended journey. The material needed to help people do something, rather than simply tell them how comprehensive the product was. A customer who understands the first task is in a better position to appreciate the larger capability later.
The portal brief connected content and use
The developer briefs translated the communication plan into requirements for the interface. They addressed what information belonged in the experience and how it should support the customer's progression. The developers retained responsibility for building the portal.
This distinction matters because onboarding friction often sits between disciplines. A page can function correctly while its instructions are unclear. A script can be accurate while appearing at the wrong moment. The work needs a shared view of the customer journey so that content and implementation reinforce each other.
Retention improved during the opening relationship
The project reduced initial friction and produced measurably higher retention over the first 90 days.
The launch brings a person to the offer; onboarding helps the person become a customer who can use it. The first weeks deserve deliberate writing and experience design because they are where a promise begins to acquire practical meaning.