Manual outreach did not scale cleanly
Teams needed a way to send personal-feeling letters without rebuilding each message by hand or losing track of recipient-specific details.
Portfolio Case Study
A privacy-safe recreation of the LetterLink portal workflow.
This case study presents a mock version of the card and letter creation flow. It focuses on the customer-facing interaction model: choose a card, customize a message, enter recipient information, and review a generated letter.
The emphasis is on the work behind the interface: reducing manual campaign setup, making merge fields less mysterious, and giving users a clear review moment before anything is considered ready to send.
Interactive Tour
LetterLink Application Workflow
Explore the actual LetterLink interface. Select a step below to walk through the core campaign management experience.
Role
Product implementation, UX recreation, frontend architecture
Stack
Laravel 11, Blade, PHP, Next.js, React, Tailwind CSS
Scope
Public demo uses mock data only; production details are private
Context
Why this demo exists
Production screenshots and client data are not appropriate for a public portfolio, so this demo recreates the core workflow with representative UI, generic card templates, and sample recipient details.
The goal is to show how the product works without exposing private records, customer names, campaign content, or backend systems.
Problem
Letter campaigns need structure without losing the personal touch.
Users needed confidence before sending
The workflow had to make templates, merge fields, recipient data, and preview output understandable before a campaign moved forward.
Privacy mattered from the start
The public portfolio version avoids client names, campaign content, production screenshots, auth flows, and backend records while still showing the interaction model.
Users
The workflow supports people who need control before scale.
LetterLink is strongest when it makes a repetitive communication task feel deliberate. The interface has to help users move quickly while still catching the details that make a letter feel personal.
Campaign operator
Build repeatable outreach without rewriting every letter from scratch.
Account team
Keep each message personal enough to feel intentional and relevant.
Reviewer
Confirm recipient details, merge fields, and send context before a batch moves forward.
Interactive Workflow
Three focused steps, no account required.
Cards
Browse representative cards and saved templates in a portal-style grid.
Create
Edit the message, insert merge variables, and enter sample recipient details.
Preview
Review the generated letter after the sample recipient fields are resolved.
Implementation
Technical choices that keep the demo useful and safe.
The production app and public demo have different responsibilities. The demo is intentionally narrow: it explains the experience without pretending to expose the underlying business systems.
- Kept the public demo frontend-only so the core workflow can be reviewed without a live backend or private data source.
- Modeled templates, recipients, campaign settings, and review checks as explicit data structures instead of hard-coded UI text.
- Used merge-variable insertion and generated previews to show how small input changes affect the final letter.
- Separated the case study from the demo route so visitors can either read the project context or try the workflow directly.
Demo Boundary
What the public version shows and what it protects.
Preserved
The public demo keeps the workflow shape: card selection, template editing, merge variables, recipient fields, campaign settings, and preview review.
Changed
Names, business records, campaign content, sender identity, counts, and visual card details are representative mock data.
Omitted
Authentication, production database records, mailing vendor integrations, admin-only screens, and client-specific reporting stay private.
Outcomes
What the project demonstrates.
For users
A guided path from card selection to recipient review that reduces uncertainty before a letter campaign is queued.
For the business
A reusable workflow for personalized outreach that can support repeated campaigns without exposing private operational details.
For the portfolio
A concrete, privacy-safe demo that shows Taylor's ability to translate a real product into a clear public artifact.
What Taylor learned
LetterLink reinforced the value of building software around the moment when a user feels uncertain. The best interface was not the one with the most controls; it was the one that made a complex campaign feel reviewable, editable, and safe to use.
Demo recreation using mock data. No client information or production systems are connected.