Our work

Projects, with the numbers

Twelve engagements across our four service lines. Details are anonymized to protect client confidentiality.

Localization

Software · A B2B SaaS company

A help center in 12 languages that stays current

The situation

The company had 1,400 help-center articles in English and a product that shipped updates monthly. Every release quietly outdated dozens of translated articles, and their previous vendor re-quoted each batch from scratch.

What we did

We set up translation memory and a shared glossary first, then ran a monthly cycle: changed articles flow to the same native-speaking linguists, only the changed segments get translated, and updates publish on a fixed date. In-context review happens on their staging site, not in spreadsheets.

Outcome

All 12 languages live within 5 months
Around 38% of ongoing volume covered by translation memory, at reduced rates
Support tickets from non-English customers dropped noticeably within two quarters

Manufacturing · An industrial equipment manufacturer

Equipment manuals into Arabic and six more languages

The situation

Safety-critical operator manuals — 900 pages of dense InDesign layouts with callouts, warning labels and exploded diagrams — needed to ship with machines into new markets, including Arabic-speaking ones where the entire layout direction flips.

What we did

Native linguists handled the text while our DTP team rebuilt each manual in the target language: mirrored layouts for Arabic, re-set callouts, re-linked diagrams. The distributor in each market signed off terminology before production, so warnings use the words local operators actually know.

Outcome

7 languages delivered, print-ready, on a single spec
Zero layout rework needed on the client side
Terminology sign-off process reused for every product line since

Healthcare · A hospital group

Patient education in five Indic languages

The situation

Patients were taking home discharge instructions and care guides written in English. Staff translated verbally, inconsistently. The group needed Tamil, Hindi, Telugu, Kannada and Malayalam versions that read clearly to patients across literacy levels.

What we did

We translated with native speakers, then simplified: shorter sentences, common words, tested with hospital staff who deal with patients daily. The DTP team handled all five scripts in both print leaflets and the patient portal, with QR codes linking print to digital.

Outcome

5 Indic languages across 40 document types
Print and portal versions from one source file
Nursing staff report fewer repeat calls about discharge instructions

Publishing

Trade publishing · A trade publisher

A 1,200-title backlist converted to ePUB3

The situation

Twelve hundred backlist titles existed only as print PDFs and aging InDesign files. Retailers were tightening validation rules, and the publisher had no consistent source files — some titles were scans.

What we did

We converted one representative title first and agreed a spec sheet against it. Then batches of 50–100 titles ran through the same pipeline: conversion, epubcheck validation, visual QA on three reading systems, delivery. Scanned titles went through OCR cleanup before conversion.

Outcome

1,200 titles delivered in 9 months
Correction rate under 0.5% across the project
Retailer validation rejections effectively eliminated

STM publishing · An STM journals publisher

40,000 journal pages into JATS XML

The situation

Decades of journal back issues — 40,000 pages with heavy mathematics, tables and references — needed to move onto a modern hosting platform that ingests JATS XML. The source material ranged from clean PDFs to scans of 1980s print.

What we did

We analysed the platform’s JATS profile, built conversion templates per journal era, and split the work: OCR cleanup and rekeying for old scans, direct conversion for born-digital files. Equations were set in MathML, references parsed and tagged. Every batch shipped with a validation report.

Outcome

40,000 pages converted and validated
Over 98% of files passed platform ingestion on first attempt
Archive now searchable and citable on the new platform

Education publishing · A K12 publisher

Making a K12 line accessible — and procurable

The situation

State procurement increasingly requires accessible instructional material. The publisher’s fixed-layout eBooks had no reading order, no alt text and failed every accessibility check buyers ran.

What we did

We rebuilt the line as accessible ePUBs: logical reading order, navigation, image descriptions written to the publisher’s editorial guidelines (and reviewed by their editors, not just ours), accessibility metadata, and validation with accessibility checkers alongside epubcheck.

Outcome

Full grade-level series rebuilt as accessible ePUB
Titles now pass buyer accessibility checks
Eligible for procurement programs that previously excluded them

e-Learning

Corporate training · A corporate L&D team

Sixty Flash courses rescued before the deadline

The situation

Browser support for Flash ended and took sixty compliance and onboarding modules with it. Source files existed for barely half. Completion records had to keep flowing into the same LMS, uninterrupted.

What we did

We triaged the library: modules with source files were converted directly; the rest were rebuilt from recordings and screenshots. Everything was repackaged to SCORM with the original completion and scoring rules, then tested on their LMS before each release wave.

Outcome

All 60 modules running in HTML5
SCORM tracking and historical completions preserved
Courses now work on tablets and phones, which Flash never did

Manufacturing · A manufacturing company

3D safety training people pay attention to

The situation

Machine-safety induction was a slide deck with a quiz. Workers clicked through it. Supervisors then re-taught everything on the floor, which took days per new hire and varied by supervisor.

What we did

We modelled their actual machines in 3D and built lockout-tagout and guard-check procedures as interactive simulations: learners perform the steps, mistakes have consequences on screen, and the course only completes when the procedure is done right. Narration recorded in three plant languages.

Outcome

Induction time on the floor cut roughly in half
Same procedure taught identically across shifts and sites
Completion and step-level performance tracked in the LMS

Higher education · A university

Six university courses built for an online semester

The situation

Six courses had to go online for the coming semester: lecture content existed as slides and notes, but nothing was structured for self-paced study, and the deadline was fixed by the academic calendar.

What we did

Faculty stayed the subject experts; our instructional designers restructured their material into storyboarded modules with knowledge checks. Animation and voice-over ran in parallel with development. Each course was packaged to SCORM and tested on the university LMS two weeks before launch.

Outcome

All 6 courses live before semester start
Single course template reused across departments since
Tracking, grading and resume behaviour verified on the LMS in advance

Technology

Government · A government department

A government portal brought to Section 508

The situation

An accessibility complaint put the department’s citizen portal under scrutiny. The portal failed basic screen-reader use, and roughly 300 frequently downloaded PDF forms and notices were untagged.

What we did

We audited against WCAG 2.2 AA, fixed the portal templates (landmarks, focus order, forms, contrast) with the Squash Apps engineering team, and remediated the PDF library to PDF/UA. Internal staff were trained to keep new documents accessible, and we retested everything after fixes.

Outcome

Portal and all 300 documents pass audit
ACR documentation delivered for procurement and compliance files
In-house team now produces accessible documents by default

Healthcare · A healthcare network

A patient portal shipped in twelve weeks

The situation

Patients phoned for everything: appointments, lab results, bills. The network wanted a portal, had been quoted a year by a large integrator, and needed it sooner.

What we did

A Squash Apps engineering pod ran the build with weekly demos: appointments with reminders, results delivery, online bill payment. We handled the accessibility pass so the portal worked with screen readers from day one — not as a retrofit. Integration used the systems the network already ran.

Outcome

Live in 12 weeks from kickoff
Call volume for routine requests fell sharply within a quarter
WCAG 2.2 AA conformance from first release

Software · A SaaS company

A dashboard redesign that cut support tickets

The situation

The product worked, but trial users couldn’t find core features, and the support queue was full of navigation questions. The in-house team was too close to the product to see why.

What we did

We ran a short UX audit — recorded task walkthroughs with real users, not opinions — then redesigned navigation and the five most-used screens. Deliverables were a Figma design system the in-house team could extend, with accessibility-first components and developer notes for the build.

Outcome

“How do I find…” support tickets down by roughly a third
Trial-to-paid conversion improved over the following quarter
In-house team now ships new screens from the design system

Want results like these?

Tell us what you’re trying to do. We’ll tell you honestly whether we’re the right team for it.