One record for the hoarding, the screen and the print job
Static OOH, digital screens and the print run that feeds them are one business — but they are almost always run as three separate tools. Nukkad holds them on a single record, with the availability, the plan, the release order, the field photo, the play log and the invoice attached to it.
- 3 channels
- OOH · DOOH · Print
- 12 modules
- one product
- Launching soon
- waitlist open
Brief, plan, place, prove, paid
Five steps, one record. Nothing is re-keyed between them, and each one hands the next what it needs.
- 01
Brief
Budget, city, window and goal — described in plain language, not a spreadsheet template.
- 02
Plan
A mix across formats and localities, with the reasoning shown — never one board booked blindly.
- 03
Place
Holds become bookings; print jobs and mounting work orders come off the same record.
- 04
Prove
Field captures and screen play logs land back on the booking they belong to.
- 05
Paid
The proof pack releases the invoice — tax, ageing and reminders already attached.
Everything an out-of-home business actually runs on
Menus are filtered per role, never restructured — so an operations lead and a finance controller recognise the same product.
Supply & inventory
One master for sites, faces and screens — and the availability chart a spreadsheet cannot hold.
Planning & discovery
Budget and goal in, a format-and-locality mix out, with the reasoning shown.
Booking & contracts
Holds that expire on their own, and the release order that binds the buy.
Execution & proof
Work orders, crews and routes — and capture-bound proof the client believes.
Screens & CMS
Loops, dayparts and share of voice on digital screens, with proof of play on what aired.
Production
Print jobs from artwork to preflight, quality check and dispatch — then the mount order.
Clients & proposals
Enquiries from wherever they arrive, and a branded proposal built from the plan.
Finance & tax
Invoices that compute, e-invoice-ready documents, ageing, dunning and partner payouts.
Measurement & reporting
Delivery, proof and modelled audience kept apart — and every number labelled for what it is.
AI engines
Eighteen of them, each with a job, an input, an output and a stated ceiling.
Roles & tenancy
Nine logins on one product; permissions granted per module, never bolted on later.
Data model
The invariants — no double-booking, no orphan proof — enforced in the database itself.
One product, filtered nine ways
The same record seen from nine desks. Nobody gets a different system; everybody gets their own view of it.
The busiest login — release order to proof pack, every campaign in flight and every exception.
Get the estate in, keep it sold, keep the calendar honest, get paid without chasing.
Say the budget, see the plan, watch the photographs land, get one invoice.
Build plans quickly, export the branded deck, reconcile delivery across many vendors.
Raise it correctly, collect it sooner, pay the partners on time.
Today's route, today's captures, today's exceptions — offline where the signal is not.
What actually plays on the screens, and the log that proves it played.
Jobs that arrive already specified, with the artwork and the dispatch address attached.
Every tenant, every module grant, every rupee of platform revenue.
The duplicate is where the money leaks
When static, digital and print live in three tools, the client, the rate and the invoice exist three times — and the argument about what ran has nowhere to be settled.
Three tools, three truths
Availability emailed from one system is stale before it is read in the next. The same face gets promised twice.
One record, one answer
Booking, print job, mount order, capture, play log and invoice all reach each other from the booking id.
Proof that settles it
The photograph and the play log are attached to the thing being argued about — not sitting in a chat thread.
- Planned as a mix
- Proof-bound execution
- Proof of play on screens
- Invoice on the same record
AI that is named, not sprinkled
Eighteen engines, each with a job and a measured ceiling. Every engine proposes; a human disposes.
Checked before a human sees it
Location, timing, duplication and creative are checked automatically. Exceptions go to a person.
Every number carries its label
Modelled, reported or measured — stated on the page, so nothing reads as more certain than it is.
One platform for every out-of-home format you buy
Get early access to Nukkad
We're opening the platform to a first group of advertisers, agencies and media owners. Join the waitlist and we'll bring you in as your city goes live.