O
Olympus
Campaign QA / browser-based

Olympus

Pre-flight QA for SMS, push and personalization. Check campaign copy, device rendering, deep links and dynamic output before launch. Files are processed locally in your browser.

3Specialized QA tools across delivery and personalization
0CRM rows intentionally sent to a backend by the suite
1Pre-flight goal: catch campaign mistakes before launch
Tools Choose the check you need
I

Atlas

SMS QA

Check encoding, true character cost and segment count. Use one-message checks, batch review or handset preview.

Manual · one messageBatch QA · campaign sheetPreview · handset
Open Atlas →
II

Apollo

Push QA + Deep Links

Check title/body truncation across devices, review campaign sheets and resolve deep links before send.

Manual · one pushBatch QA · campaign sheetPreview · iOS / AndroidDeep links · resolve + QR
Open Apollo →
III

Poseidon

Personalization QA

Test template tokens against QA profiles and surface missing values, fallbacks and exact rendered output.

Profiles · CSV / Excel / JSONMapping · source → tokenReview · failed / fallback / ready
Open Poseidon →
Why it exists

Because the errors are small, and they ship anyway.

An emoji drops an SMS from 160 characters to 70. A title two words too long is cut mid-sentence on the one phone nobody tested. A merge field with a capital letter renders as a hole in the message. None of it shows up in a spreadsheet, and all of it reaches a customer.

Each tool owns a different pre-flight question: will the SMS send correctly, will the push display correctly, and will personalization resolve correctly for every QA profile? The suite processes the campaign data you load locally in the page rather than sending it to its own backend.

On the names. Atlas carries the weight of SMS constraints, Apollo watches what reaches the screen, and Poseidon deals with what sits beneath the surface: customer data and dynamic content. Together they form the Olympus CRM QA suite.

Who built this

Made by a CRM manager, for mobile messaging.

I am Buse Sahin, a CRM manager and CRM automation manager based in Berlin, working on lifecycle and mobile messaging programmes — SMS, push notifications and personalized campaigns across a lot of markets at once. My background is in CRM at HelloFresh and before that Sony.

Olympus came out of that work. Every tool here exists because the same class of mistake kept reaching customers: a character count that was right in the spreadsheet and wrong on the handset, a push that read fine on a big phone and clipped on a small one, a merge field that resolved for the test profile and nowhere else. Nothing in the suite needs an account or a backend, because CRM data should not have to leave the browser to be checked.

If you run CRM, lifecycle or mobile messaging and any of this sounds familiar, take it and use it — or get in touch.