Copy coach
Built a “Copy Coach” GPT that turns Deputy UI screenshots into tone-aligned copy options, adopted by >50% of the design team and reducing copy-related feedback in design reviews.
Built a “Copy Coach” GPT that turns Deputy UI screenshots into tone-aligned copy options, adopted by >50% of the design team and reducing copy-related feedback in design reviews.
2025
Product Design Manager
Deputy
B2B SAAS
Copy was written late and was inconsistent, leading to a continuous loop of rewrites and reviews and causing delivery delays.
Manual copy entry was too slow; building a Figma plugin/MCP integration was too heavy for the problem
How do we make our tone standards executable and output immediately usable in design files?
I took Deputy’s existing tone-of-voice guidelines and translated them into a structured Markdown ruleset
This includes do/don’t rules to calibrate outputs
Key content principles have been turned into repeatable checks (brevity, task-first language, consistent terminology)
The user uploads a screenshot of their design, it is combined with Deputy's tone of voice guidelines and examples of good/bad copy to come up with copy suggestions
Generated rewrites are grouped by UI element (titles, labels, helper text, CTAs, errors)
Multiple options are always given so designers can decide which direction is more appropriate
Avoided manual copy entry (too high effort) and avoided a plugin/MCP build (too complex)
Preserved layout context (hierarchy, labels, intent) with minimal friction
Made it easy to run repeatedly during iteration
Positioned as a pre-review step to catch copy issues before critique
Created a repeatable loop: draft UI → run GPT → paste + adjust → review
Reduced copy feedback without adding meetings or dependencies
Built a “Copy Coach” GPT that turns Deputy UI screenshots into tone-aligned copy options, adopted by >50% of the design team and reducing copy-related feedback in design reviews.
2025
Product Design Manager
Deputy
B2B SAAS
Designed the end-to-end WFM flow:
Roster → timesheets → pay run → payslips
Made the first pay run easy to complete (guided steps + clear next actions)
Surfaced value fast with confident review states (so teams can onboard without support)
Designed the end-to-end WFM flow:
Roster → timesheets → pay run → payslips
Made the first pay run easy to complete (guided steps + clear next actions)
Surfaced value fast with confident review states (so teams can onboard without support)
Designed the end-to-end WFM flow:
Roster → timesheets → pay run → payslips
Made the first pay run easy to complete (guided steps + clear next actions)
Surfaced value fast with confident review states (so teams can onboard without support)
Avoided manual copy entry (too high effort) and avoided a plugin/MCP build (too complex)
Preserved layout context (hierarchy, labels, intent) with minimal friction
Made it easy to run repeatedly during iteration
Designed the end-to-end WFM flow:
Roster → timesheets → pay run → payslips
Made the first pay run easy to complete (guided steps + clear next actions)
Surfaced value fast with confident review states (so teams can onboard without support)
Built a “Copy Coach” GPT that turns Deputy UI screenshots into tone-aligned copy options, adopted by >50% of the design team and reducing copy-related feedback in design reviews.
2025
Product Design Manager
Deputy
B2B SAAS
Copy was written late and was inconsistent, leading to a continuous loop of rewrites and reviews and causing delivery delays.
Manual copy entry was too slow; building a Figma plugin/MCP integration was too heavy for the problem
How do we make our tone standards executable and output immediately usable in design files?
I took Deputy’s existing tone-of-voice guidelines and translated them into a structured Markdown ruleset
This includes do/don’t rules to calibrate outputs
Key content principles have been turned into repeatable checks (brevity, task-first language, consistent terminology)
The user uploads a screenshot of their design, it is combined with Deputy's tone of voice guidelines and examples of good/bad copy to come up with copy suggestions
Generated rewrites are grouped by UI element (titles, labels, helper text, CTAs, errors)
Multiple options are always given so designers can decide which direction is more appropriate
Avoided manual copy entry (too high effort) and avoided a plugin/MCP build (too complex)
Preserved layout context (hierarchy, labels, intent) with minimal friction
Made it easy to run repeatedly during iteration
Positioned as a pre-review step to catch copy issues before critique
Created a repeatable loop: draft UI → run GPT → paste + adjust → review
Reduced copy feedback without adding meetings or dependencies