# ExperientialOS — Full FAQ > Full-service custom build studio for brand activations, festivals, conferences, and live experiences. Software under ExperientialOS, hardware under our sister brand PivotXP (https://pivotxp.com), one accountable team. We are a build studio, not a SaaS platform. This file is a plain-text dump of the FAQ at https://experientialos.com/faq, formatted for LLM and AI agent consumption. The same content is rendered as Schema.org FAQPage JSON-LD on the canonical page. --- ## Section 01 — About ExperientialOS ### What is ExperientialOS? ExperientialOS is a full-service custom build studio for live experiences. We design, build, and run the software that powers brand activations, festivals, conferences, and brand tours — and we build the hardware to run it on through our sister brand PivotXP (https://pivotxp.com). One team, one accountable partner, software and hardware from a single source. Custom-built for your specific event, never configured from a template. ### Who do you build for? Brand teams (CMOs, brand directors, brand experience leads), experiential agencies, event production companies, and enterprise marketing teams. If you're putting on a real-world event with a real audience, we probably build for you. ### What kind of company are you? Full-service. We design and build the software side under ExperientialOS, and we design and ship the hardware under our sister brand PivotXP (https://pivotxp.com) — registration kiosks, RFID and NFC readers, photo capture rigs, custom on-site equipment. The same team owns both. What we don't do is creative direction, art direction, or production design — we work alongside your creative agency on those. ### How big is your team? Small and senior. Every project is staffed with a tight team of experienced engineers who run discovery, build, and on-site support themselves. There is no offshore handoff, no junior bench, and no account manager between you and the people writing the code. --- ## Section 02 — What we build ### What kind of software do you actually build? Six core systems we tune to every event: registration and check-in, a live ops command center, vendor and touchpoint APIs, access control and VIP rules, photo and content delivery, and analytics and insights. You can take all six or just the modules you need. ### What types of events do you support? Brand activations, festival activations, multi-city brand tours, conferences and summits, VIP and hospitality experiences, experiential retail (pop-ups, flagship launches), sports and fan zones, and sponsor activations. Any live experience where guest data, vendor coordination, and on-site ops need to work together. ### Can you handle multi-day or multi-city events? Yes. Most of what we build runs for multiple days, and many builds run for weeks across multiple cities. The system is designed for tour-style events where vendors, staff, and inventory move between markets — but the data stays unified across every stop. ### Can you integrate with photo booths, RFID hardware, and other vendors? Yes. We've shipped integrations with photo capture vendors, RFID and NFC hardware, SMS and email providers, CRMs and CDPs, and custom on-site equipment. If your vendor doesn't have an integration yet, we write one — usually within the same sprint. ### Do you build hardware too, or just software? Both. Our hardware capability lives at our sister brand PivotXP (https://pivotxp.com), where the same team designs, sources, and deploys custom RFID readers, NFC wristbands, photo capture rigs, registration kiosks, scanners, and bespoke on-site installations. Hire us for the software, the hardware, or both — and you have one accountable partner and one invoice instead of stitching together five vendors. ### Can you build the guest microsite too? Yes. Every guest gets their own personal microsite with their journey, their photos and content, their unlocks, and any deliverables you've promised them. It's branded to your event and updates live as they move through the experience. --- ## Section 03 — Process and speed ### How fast do you reply when I reach out? Within hours, not days. A real software engineer reads your message and writes back with a real scope — usually the same day. There's no form-routing bot and no sales drip. ### How long does a typical build take? Two weeks from kickoff to live, for most builds. The system goes from "we agreed to work together" to "your event is running on it" in fourteen days. Bigger or more complex builds can run longer, but two weeks is the norm. ### What does your discovery and kickoff process look like? We talk to you (not a sales rep), scope the work together, agree on price, and start building. No discovery deck handoff. No multi-week paid discovery phase. We send you regular demos through the build and we ship what we agreed to. ### Are you on-site during my event? Yes — every day your event is live. The same engineers who built your software are on-site when the doors open and every day after that. One-day pop-up or two-week tour, we're there. ### What happens after the event ends? You get a branded executive recap delivered the next morning, full data export, and a debrief. We stay on between events to evolve the system for the next one — improvements ship between shows, not between quarterly releases. --- ## Section 04 — Working with us ### Can you white-label your work for an agency? Yes. We work with experiential agencies who want a custom software partner without giving up the client relationship. The build is yours to present, the system runs in your account, and we stay in the background or join client meetings — whichever you prefer. ### Do you work with experiential agencies and production companies? Yes — agencies, production companies, and brands directly. Agencies and producers are some of our favorite partners because they know exactly what they need and we can move fast without a translation layer. ### Do you have a minimum project size? Not a strict one. We've shipped one-day pop-ups and multi-week tours alike. The right-fit project is one where the brand cares enough about the experience to want it custom-built — not a $200 ticketed event where a stock platform would do the job. ### How do you price projects? Every project is custom-scoped. Pricing is generally a one-time build fee plus a simple monthly support fee for the time we're running and supporting your event. No per-attendee fees, no per-event seat licenses, no surprise overage charges. We tell you the number before you say yes. --- ## Section 05 — Data, security, and compliance ### Where is my guest data stored? In your accounts — your cloud, your region, your keys. Your data lives in an isolated environment with your name on it. We don't share storage across clients, and we don't train models or build other products on your data. ### Do you sign DPAs and security questionnaires? Yes. We've signed enterprise DPAs and answered formal security questionnaires for brands with serious legal teams. Send us your standard agreement and we'll respond with redlines or a signature within hours. ### Are you SOC 2 compliant? We follow SOC 2 controls in the way we build and operate, and we can share specifics about our security posture on request. For builds that need a formal certification (SOC 2 Type II, HIPAA, ISO 27001, FedRAMP), we scope the deploy accordingly. Tell us your specific compliance requirements and we'll respond specifically. ### How do you handle PII and waivers? Field-level encryption at rest, TLS 1.3 in transit, role-based access on every read and write, full audit log on every record. Waivers are captured at check-in, signed digitally with timestamp and IP, and stored as PDFs in your tenant. --- ## Section 06 — How we're different ### How are you different from Swoogo, Cvent, Bizzabo, and Splash? Those are configurable SaaS platforms. You pick a template, customize the fields, and work around the limits of their data model. We're a custom build studio — software, hardware (via PivotXP at https://pivotxp.com), and the team that runs both on-site. We architect a system for your exact event, ship it in two weeks, and run it with you on event days. A different category of company entirely. ### Why custom software instead of a configurable SaaS? Because no two brands run the same kind of activation, and the small details — the way your guests check in, the way your vendors hand off completions, the way your team gets paged when a queue forms — are exactly the things a template can't accommodate. Custom software is shaped by the room. Templates aren't. ### We already use Eventbrite or Splash — can we still work with you? Yes. A lot of brands use a stock platform for ticketing or basic registration and hire us for the parts that don't fit a template — the experiential moments, the on-site ops, the vendor integrations, the post-event recap. We integrate with most major platforms, so we can be the layer that handles everything stock SaaS can't reach. --- ## Contact - Email: hello@experientialos.com - Phone: (704) 284-7155 - Address: 328 Zimmer Road, Fort Mill, South Carolina 29707 - Website: https://experientialos.com - Start a project: https://experientialos.com/contact