We rebuilt a community FM station as a 24/7 digital platform in 12 weeks. Here's what it unlocked.
Greek FM went from a single Melbourne FM transmitter with no digital presence to a 5-surface 24/7 AI-hosted platform in 12 weeks. The business outcomes, the capability upgrade, and what every community station should be paying attention to.
A year ago, Greek FM Radio was what most community stations are: one FM transmitter, a loyal but invisible audience, on-air ads, zero listener data. Today it runs 24/7 across five surfaces (web, iOS, Android, Chromecast and PWA) with bilingual voice agents, a concierge that takes song requests and dedications by phone, and a proprietary content engine that produces fully-mastered long-form shows end-to-end.
Twelve weeks of solo delivery. This is the outcome story — the business capability upgrade, not the implementation cookbook.
The before
Before we started, the station had what thousands of community broadcasters have:
- One transmitter on an FM frequency in Melbourne
- Loyal local audience but no idea who they were beyond demographic guesses
- On-air ads only, no digital ad inventory, no sponsor portal, no reporting
- No website worth calling a website (a single page with a mission statement)
- No way to grow outside the FM footprint
Sound familiar? This is most community radio. The medium hasn't changed since the 70s.
The brief
One sentence: take this station digital, end-to-end, keep the soul, ship it in one quarter.
Constraints:
- One operator. No team. I build, the founder approves.
- Own the code. No vendor lock-in. No revenue share. No monthly SaaS fee eating margin.
- Bilingual. The audience switches between Greek and English mid-sentence. So does the product.
- Work on nonna's iPad. Not a dev-tools audience.
What shipped
Instead of a build checklist, let me describe what the station can now do that it couldn't 12 weeks earlier:
24/7 programming, no dead air
A proprietary content engine produces fully-produced long-form shows on a rolling schedule. Station IDs, ad beds, music transitions, tonal consistency, broadcast-grade mastering. The real human DJs keep doing what only they can (interviews, live events, community moments); the engine fills the gaps and runs overnight.
Bilingual voice concierge by phone
Two voice agents answer the station line, in Greek or English, whichever the caller opens with. One handles listener service (song requests, dedications, contests, Top 20 votes). The other handles business development (sponsor inquiries, directory submissions, after-hours leads). They hand off to each other mid-call if the context shifts. Every call is transcribed and surfaced in the admin CRM for post-call review.
Cross-platform streaming on five surfaces
Same codebase, five destinations:
- Web (progressive web app, installable on iPhone and Android)
- iOS native
- Android native
- Chromecast (one-tap cast to every TV in the house)
- Smart speakers (via existing directories)
Sponsor & revenue operations
Sponsors have a self-serve portal. They can see impressions, click-throughs on directory entries, campaign performance. The station can charge premium rates because there's actual reporting.
The Agora (Greek business directory)
Local Greek businesses list themselves. The directory is searchable, location-aware, and integrated with payments so businesses can pay a small fee to boost visibility. A new revenue line that didn't exist before.
Merch store
Headless commerce integration, on-brand, checkout in under 30 seconds.
Top 20 chart + voting
Public chart. Listeners vote (via the site, the app, or by calling the voice agent). Updated weekly, promoted on-air.
Event engine
Station-run events and community events both live on the platform. RSVP-able. Optional ticketing.
Contest engine
Contests can be launched by admins in minutes. Entries come in via web, app, and voice. Winners get notified automatically.
Admin platform
22 purpose-built admin screens cover everything: schedule, content, sponsors, listings, contests, analytics, uptime monitoring, AI assistant, voice-call CRM.
The scale of the build
I can't walk through the implementation specifics — those are trade secret and protected. What I can share is the shape:
- A production database covering schedule, content, listeners, sponsors, directory, analytics and voice CRM
- A comprehensive public + admin API surface
- Proprietary voice agents embedded in the station's live operations
- Cross-platform native apps sharing a common component system
- Broadcast-grade audio post-production with internal quality gates
- Full observability and automated monitoring
The total build complexity is comparable to an enterprise SaaS product. Compressed into 12 weeks of solo delivery because modern tooling and the one-operator model make it possible.
The numbers that matter
Things I can share:
- Zero dead air since launch
- Voice agent answers in under 3 rings, 24/7, bilingual
- Fully-produced long-form shows generated in minutes (the exact multiplier is covered under scope NDA)
- Code-complete in 12 calendar weeks, solo
- Owned outright — no SaaS subscription, no revenue share, the client can walk away with the whole system tomorrow
Business outcomes (sharing only what the client has blessed):
- 5 new revenue lines that didn't exist before (directory boosts, premium sponsor placement, events ticketing, merch, sponsored content)
- 24/7 sponsor and listener inquiry capture (vs 0 outside business hours previously)
- Growing audience data (who's listening, what they like, when, from where) where there was literally none before
Why it worked (the honest version)
Three things, in order:
1. One operator. No handoffs. No "the devs said" vs. "the strategist said" vs. "the agency said." The person writing the spec is the person writing the code is the person mastering the audio. This is the fastest possible way to ship, and the only reason a 12-week timeline was plausible.
2. AI-accelerated but human-reviewed. Every output — code, copy, audio — gets AI-assisted in the first pass and human-tuned in the second. You can tell the difference. Customers can tell the difference.
3. Own the pipeline. Every layer of the tech stack is something the client can migrate off tomorrow without losing the system. No proprietary middleware. No "Pulse Radio OS cloud" subscription extracting rent forever. You buy the build, you own the build.
What I'd do differently
- Admin UX upfront. We built 22 admin pages. The first 10 would have saved 100 hours of rework if they'd been designed as a system, not as emergent needs. Now the Pulse Radio OS template ships with those baseline screens from day one.
- Music library pre-processing from day one. We normalised the whole music library at week 4. Should have been week 1.
- Sponsor portal V2 before V1 was live. Not a regret, but the first version didn't do campaign reporting well enough to charge premium rates. That's now a standard feature from the start on every Radio OS build.
Who this is for
If you're a community station, a podcast network thinking about going linear, or a brand that wants to become media — Pulse Radio OS is delivered as a managed service. We host the platform, run the day-to-day ops, automate the programming, and handle the cross-platform delivery. Three ways to buy:
- Managed SaaS from AUD $2,500/mo (12-month min) + one-time $12-20K setup — we host and operate the station for you
- Whitelabel License from AUD $85,000 one-off — own the whole platform, self-host or cloud, fully customised
- Enterprise / Network POA — multi-station, multi-language deployments
Every engagement starts with a 30-min demo. Fixed-scope quote within 48 hours.
FAQ
Q: Can Pulse Radio OS work in languages other than Greek or English? A: Yes. Our voice layer supports most major world languages. Greek FM just happens to run bilingual GR/EN because that's its audience.
Q: How much does running the content engine cost per month? A: Covered under scope NDA. Ballpark: a fraction of what a single human producer's hourly rate would be for equivalent output.
Q: Can you integrate with my existing broadcast chain? A: Yes. Most standard broadcast software integrates cleanly. The streaming layer is swappable.
Q: What happens if the underlying tech suppliers change their pricing? A: The stack is designed to swap. The voice layer, the reasoning layer, and the content pipeline are all portable. You're not locked to any single vendor. That's the point of owning the code.
Q: How do I start? A: Book a 30-min strategy call and I'll come with a fixed-scope quote within 48 hours. Or run the AI scope generator and get a draft proposal in 10 seconds.
Got an AI project in mind?
I'm Nikolaos. I build the kind of systems I write about — solo, end-to-end, Melbourne. 30-min call. Fixed-scope quote in 48 hrs. No decks.
Voice AI for dental clinics: why reception is the first 4 hours you should automate
Most Melbourne dental clinics burn 4+ reception hours a day on the same 8 call types. A 24/7 voice agent books, reschedules, sends reminders, and triages emergencies for under $50K. Here's the math.
What my prospects feel, not what my builder built
A prospect books a call. Sixty seconds later they have a briefing about their own business. I walk in having studied them for a week. Neither of us wastes time.
Pulse.AI is taking bookings. Promo + Pro Packs inside.
Pulse.AI is officially open. Launch promo for the first 20 clients. Industry Pro Packs for tradies, hospo, small biz, lead gen and e-comm from $4,500. Consulting from $350/hr. Here's what's on the menu.