wdye studio
[ our own software, and an honest answer about when to use it ]
we spent years building events inside other people's platforms. the gap we kept hitting was the same one every time: a $99 template that cannot carry a real conference, and a $40,000 enterprise contract that is absurd for a 300-person annual meeting. studio is the thing in the middle, and we built it because we needed it.
the actual decision
software, a human, or both
this is the question worth answering before you look at any feature list. we make money either way, so here is the honest version.
| what you need | hire us | use studio | enterprise platform |
|---|---|---|---|
| tiered member pricing, POs, CE credit, exhibitor sales | yes, in your platform | no | yes |
| a genuinely good event website and attendee app | yes | yes, and it is the core of the product | usually, at extra cost |
| how much of your time it takes | a kickoff call and a review | an afternoon, then edits whenever you like | weeks, plus training |
| how you pay | project fee, fixed by scope | per event, no annual contract | annual contract |
| who fixes it at 9pm the night before | we do | you do, in a couple of clicks | a support ticket |
| best fit | conferences with real registration complexity | meetings, summits and conferences with 2,500 attendees or fewer that need to have a top-tier website and event app | large portfolios with onsite badging |
use studio if …
- you do not already own a registration platform and do not want an annual contract
- the event needs to look excellent more than it needs 14 pricing rules
- you want an attendee app without a second vendor
- you would rather make changes yourself at 9pm than file a ticket
hire us instead if …
- you already pay for EventSquid, Swoogo, Stova or eventPower
- your pricing has members, tiers, comps, groups and purchase orders in it
- your conference has abstracts, CE credit or exhibitor sales
- the honest constraint is your time, not your software
what it actually does
a real event site and an attendee app, from one build
you set the event up once. the website and the app read from the same content, so the agenda cannot disagree with itself.
- event website with agenda, speakers, sponsors, venue and travel
- an AI agenda assistant that turns your existing schedule into structured sessions
- speaker and sponsor portals so they submit their own content
- an attendee app with live bulletins, personal schedules and offline agenda access
- session Q&A with moderation, and live polls with results on screen
- QR badge scanning that saves contacts both ways and exports as a lead list
- private preview before launch, so nothing is public until you say so
full feature detail and current pricing live on wdyestudio.com, which is where you would sign up.
or take both
the most common thing that actually happens: your registration lives in the platform you already pay for, and studio runs the website and the attendee app on top of it. we build both sides and you deal with one person.
you might be wondering …
studio questions
is studio a registration platform?
not in the enterprise sense. studio builds your event website and attendee app, and handles the attendee-facing experience beautifully. if your event needs member and non-member pricing tiers, purchase orders, CE credit tracking and exhibitor sales, you want a full registration platform, and you want us to build it in one.
do we have to use studio to work with you?
no, and most clients do not. the default engagement is us working inside the platform you already pay for. studio exists for the people that model does not serve.
can you build it in studio for us?
yes. plenty of clients want the studio product but not the afternoon it takes to set it up. that is just a normal project for us, priced like any other build.
what does it cost?
per event rather than per year, which is the point. you can build a complete site for free and only pay when you decide to publish it, so you can see exactly what you are buying first. current pricing is on wdyestudio.com.
not sure which one you need?
describe the event in three sentences. we will tell you whether it is a studio job, a platform build, or both, and we will tell you if it is neither.