The modules an out-of-home business actually runs on

One master record for every site, face and screen — latitude and longitude, size, format, illumination, traffic direction, photographs and ownership. Bulk import from the spreadsheet you keep today, hundreds of assets in one pass. Assets grouped into sellable packages, corridors and clusters. Rate cards held in the platform per asset, per season and per client tier, with minimum durations and lead times. Municipal permits, licence renewals, structural certificates and insurance as dates on the asset, with alerts before they lapse and an optional hard block on booking a lapsed asset. Landlord and lease terms with rent, escalation and renewal dates. A maintenance and incident log per site. Stale-listing and missing-photograph warnings so the estate does not quietly rot.

One availability ledger per face, by fortnight, that your whole team sees at once. Holds and options expire on their own with a named owner and a countdown, so nothing sits reserved because an enquiry went quiet. Double-booking is prevented by the system rather than by three people checking three files. Seller-set lead times, blackout dates and seasonal restrictions per asset. Renewal reminders before a campaign lapses, and alerts when a face a client wanted frees up.

A booking that carries its client, its assets, its dates, its rate and its documents. Release Order in India, Insertion Order in the United States, produced as a real document with e-signature. Approval chains by client, office, role or budget, recorded against named people. A campaign dashboard with pacing and delivery against what was sold. Pause, resume and edit after go-live; clone a campaign for the next cycle; batch creation for multi-city rollouts. An activity log with per-action revert.

Five seeded roles — Owner, Sales, Operations, Finance and Field — plus client and field-worker logins, and a role editor for your own catalogue. Data scope per role per area: own, team, city or all. Task assignment and a daily worklist per person. Invite staff, clients and crews by email or phone with the role on the invite. Staff can be suspended and reactivated rather than deleted, and the system always keeps at least one owner. Two-factor authentication required for anyone who can approve payouts, manage roles or see margin. A per-tenant audit log of who did what, to which record, when.

A client record with company, contacts, GSTIN, billing address, payment terms and credit limit — and one page per client showing campaigns, quotations, invoices, outstanding and messages. Enquiries from the website, email or WhatsApp land in one queue with source attribution and deduplication. A sales pipeline by stage with expected value and team targets. Proposals generated from a selected site list into branded PPT, Excel or PDF, with client-safe rates. WhatsApp as a first-class channel for approvals, proof delivery and reminders. Contact details are masked with a logged reveal, and bulk contact export does not exist at the API — a deliberate protection, not a permission setting.

Mounting and maintenance work orders with due dates and dependencies, including whether the printed material has actually been delivered. Crew assignment and optimised routing for the day. Capture happens in the app only, GPS-locked to the booked face, geofenced, and stamped with the server's time rather than the phone's. Duplicate and recycled photographs are detected across your whole account. Captures queue offline and sync when signal returns. Escalation when a proof is late against its SLA. A branded proof pack per campaign that your client can open.

Screens as inventory alongside static faces. A creative library with approval status, automatic spec validation on upload, and checks against each screen’s accepted specifications. Loop scheduling with dayparting, recurrence and share of voice. Maker-checker approval before go-live, with a second sign-off for the venue where one is wanted. Time-based dayparting uses the published operating schedule. Offline playback and edge caching. Remote commands for supported players include reload, display on/off, volume and brightness, with command acknowledgement and device health alerts. A play log per screen and per spot, exportable and reconcilable against the loop that was scheduled.

Print jobs priced on area, media and finishing with quantity breaks and a minimum-charge floor. Preflight on the artwork — resolution at final size, colour mode, bleed, outlined fonts, dimensions — reported in plain language. A failed preflight blocks the press; a warning needs a named person to accept it. Client-approved soft proofs with a timestamp. Machine and operator assignment, photographed quality check, dispatch with docket and delivery evidence. Wastage and reprints recorded against the job. A delivered job flips its mounting work order to material-ready. Jobs can be routed to a partner press, who accepts with a promised date and never sees the end advertiser or your margin.

Invoices raised off the booking and released by the proof pack, so what ran and what is billed are the same record. GST-correct and e-invoice-ready, with place of supply computed per line and withholding tax held as data rather than hard-coded. Client ledger, ageing, credit limits with an optional hard block, debit and credit notes, and receipts. Landlord and lease revenue share on fixed, variable or share terms. Vendor and crew payouts with earned, paid and outstanding per job. Document numbering series per document type per financial year. Multi-currency and per-market formats.

Occupancy and utilisation by asset, format and month. Site profitability against lease, maintenance and licence cost. Revenue by client, by salesperson and by city. Vendor and crew performance benchmarking. Campaign delivery with modelled impressions, labelled as modelled and never presented as measured. A custom report builder, saved configurations re-runnable on a new date range, scheduled email delivery, CSV export and a reporting API separate from the interface.

Your workspace is your own: no tenant ever sees another tenant's data. Your company profile, GSTIN, addresses, bank details, logo and signature carry onto every document. Your branding applies to the client portal and every PDF and public link. Editions per channel — OOH, DOOH, print — resolved server-side. Self-service data export of clients, inventory, bookings, invoices and messages as CSV, on demand, without asking us. A public REST API over OAuth 2.0 and TLS, single sign-on, rate limiting, and India data residency as a deployment choice.

Site-mix planning, rate recommendation, occupancy forecasting, proof-image checking, duplicate detection, route optimisation, invoice reading and collections risk — each a named feature with an input you can see and an output you can correct. Every engine proposes; a person disposes. No accuracy figure is published that we have not measured on our own data, there is no camera-based audience or demographic measurement, and dayparting rules are called scheduling rather than AI.

The data model is built to the OpenRTB 2.6 digital-out-of-home objects and the OpenOOH venue taxonomy, and screens carry floor prices, category blocklists and network-versus-venue restriction precedence. Exchange and supply-side partners are under evaluation and none is integrated yet, so nothing here claims one. When an integration ships it will be named on this page, with its date.