MNM Nexus: An Accounting App as a 30-Second Vertical Demo

MNM Nexus is an app that keeps the books for rideshare drivers who work as a PFA, the Romanian status for a self-employed sole trader. The app tracks income and receipts, estimates the year’s taxes, warns before the CAS threshold, pre-fills payment orders and keeps the PFA’s documents in one place.

MNM Nexus already had a vertical presentation of the app: 27 seconds of still slides, with no sound. The brief was a better replacement: a 30-second vertical demo for drivers, with the hook in the first second, then the real app screens building up, from income to the tax alert, tax estimates and paperwork.

We delivered one film in 9:16, at 1080 × 1920 and 30 frames a second, in Romanian, with an original score. MNM Nexus agreed to let us show it here and on our client work page.

The demo had four problems to solve at once.

• The subject is dry. Accounting is numbers and forms. Nothing in it moves unless you make it move.
• The screen is small. On a phone, every caption competes with the app it describes.
• The sound is often off. Many people scroll muted, so the story has to read without the music.
• The numbers are money. In a finance app, a made-up user count or a real driver’s details on screen would undo the film.

A plain screen recording tends to bring small text, a busy account and taps with no rhythm. So we rebuilt the screens instead.

The film is in Romanian, for drivers in Romania. Here is what each caption says, and what the phone shows.

CAS and CASS are the pension and health contributions, as the app labels them. The CAS threshold is the yearly profit above which, the app explains, the pension contribution becomes mandatory. An OP is a payment order, which the app pre-fills for paying taxes to ANAF, Romania’s tax authority.

A hook on the first frame. The first words are on screen from frame zero, so the feed never shows an empty frame. They name the platforms drivers work for, with “Uber” and “Bolt?” in the biggest type in the film, underlined in the app’s violet.

The real screens, rebuilt from the app’s code. We rebuilt the start, home, taxes and profile screens in HTML and CSS from the app’s SwiftUI views, with the colours from its theme file and the logo from its own mark. The interface text stays exactly as the app writes it, without Romanian diacritics (“Taxe si contributii”); only our captions use them. Rebuilt screens stay sharp at full size, and every number can count up on the beat.

Big captions for sound-off feeds. One idea per caption, in heavy type at the top of the frame, above the phone rather than over it. Each caption has one accent word in violet, such as “CAS.” or “automat.” The phone shows the proof; the caption says what it means.

An original score, cut to every tap and number. We wrote the music in code, at 120 BPM in D minor, with no samples. Each scene cut sits on a bar line, and every word, count, notification, tap and swipe lands on the frame of its sound. A sixteenth of silence comes just before the logo lands.

Vertical 9:16. It was in the brief, and it is the shape of Reels, TikTok and Shorts. It gives the phone most of the frame’s height, with the caption above it.

A finance app lives on trust, so the film says only what the app already says.

• No invented numbers. No user counts, reviews or other figures passed off as real. The figures are the app’s demo data: the example account, Andrei Popescu, from the client’s own presentation.
• No personal details. We took the demo account’s email and phone off the profile screen.
• No borrowed logos. Uber and Bolt appear as names, the way the app mentions them.
• No claims beyond the app. The CAS alert, the tax estimate, the pre-filled payment orders and the missing-documents warning are all things the app does.
• No store badges we could not link. We did not find the exact store links in the app’s code, so the end card names the stores in text, without the official badges.

None of this is specific to accounting. For a demo of your own app, this is the list we work from.

• Name your user or their problem in the first frame, in their words, with words on screen from frame zero.
• Show the real app with demo data: rebuild or record your actual screens, and strip anything personal.
• Give each feature one caption and about four seconds.
• Put one accent word per caption in your brand colour.
• Keep the interface text exactly as the app writes it; only the captions are yours to write.
• Give every tap, count and notification its own sound, on the frame it happens.
• End on the name, the one-line promise, the address and where to get the app.
• Watch it once with the sound off before you post.

In loudscene, the Feature demo template puts one feature in a phone, tap by tap, with the hook in the first two seconds. Find it in the e-commerce and SaaS pack or on our page for SaaS teams. For the method, read how to turn your website into a video; for vertical safe zones, the Reels, TikTok and Shorts specs; for a 16:9 launch film, our CHIT case study.