Five platforms, six months: How GetWyz built a copy system for a regulated mortgage product

Industry: Fintech / mortgage

Team: 12 engineers, one product/design lead owning copy end-to-end

The trigger

GetWyz acquired the Mobelux mobile team to accelerate app development. Mobelux had a React prototype, a team of web developers who'd never shipped a native app, and a deadline: get at least two platforms live within six months.

Mortgage products come with volume. iOS, Android, web, a marketing site, and a text-heavy product with legal and compliance requirements stacked on top. Plus, GetWyz’s founder doesn't sign off on design direction with placeholder copy. Every Figma screen needed to show real, current text — not lorem ipsum — while multiple people worked in it at once.

Jeff Rock, Director of Product Design, looked at managing that in Google Docs, Sheets, or Notion and ruled it out immediately: "There's just no way it was going to give us what we needed."

The build

GetWyz runs a design-driven process:

1. Product and design build in Figma.
2. Jeff connects the Figma file to a Ditto project and assigns developer IDs (the unique identifiers engineers use to reference text in code) as he goes. Engineering never has to think about naming or structure.
3. A dedicated copy owner on the CS team, given full authorship, works exclusively in the Ditto Web App with editors and subject-matter experts to get every string right.
4. Once every text item is marked final, Jeff tells engineering.
5. Engineering pulls the text items via Ditto CLI roughly 30 minutes before each weekly release.

With Ditto, engineering has close to zero day-to-day involvement in copy. "They just don't really need it," says Jeff. "They run the CLI right before they put out a build." One weekly touchpoint, for a full mortgage application flow shipping across five surfaces.

What that unlocked

• Two platforms live within a six-month deadline — the original constraint that led them to look for a copy solution.
• Web and iOS already running on one shared set of strings — no duplicate copy to maintain per platform.
• A team of 2–3 engineers building a compliance-heavy product without a dedicated localization or content engineering hire — copy work is absorbed by Jeff and one CS-side copy owner, not by headcount.
• One CLI pull per weekly build is the entire engineering footprint of the copy process — no manual string handoffs, no export/re-import diffing.

For Jeff, the most important win of their Ditto workflow is the compounding benefit for the whole team: "This tool is making 20 people's lives 80% easier."

In Jeff's words

“Ditto helped us create a scalable, sustainable solution for turning Figma into a consistent source of truth for not just UX, UI, and engineering, but copy as well.”

"If you're dealing in medical, legal, fintech — any of these regulated spaces, you're always dealing with multiple teams that all have to coordinate. And people are emailing documents and you've got sheets out of date and naming conventions that are wrong. This just wipes all that away."

Where it's headed

GetWyz is still doing a lot of the setup and developer ID generation manually, while they get the hang of the process. Since regulations leave no room for error, Jeff is cautious about handing that work to AI agents.

But Ditto’s expanded MCP, which lets AI agents work directly in Ditto, makes it possible to automate initial project setup and generate developer IDs in bulk, following prescribed conventions. Jeff is looking to unlock those efficiency gains in his own time, once the right processes and guardrails are in place.