What happens to last year’s data?
▸
It stays, and it compounds. Your entrant list, your nominations, your votes and your published winners belong to the project rather than to one season, so year five still shows year one — which is what makes a business able to say “winner five years running”. If you stop paying, you keep the period you have paid for and the account then goes dormant: the admin turns read-only and badge kits stop resolving. Nothing is deleted, and turning it back on restores it exactly as it was. One thing worth saying plainly — today a dormant account’s public winners directory stays up rather than going dark. The switch to take it down is written and deliberately not turned on.
Can we use our own domain?
▸
Yes — that is the point of the product. The contest and the winners directory run on your hostname, so the links, the search traffic and the archive accrue to you and not to us. Being exact about how it works today: there is no self-serve domain screen yet. You point a CNAME at us and we set the hostname and its certificate up with you during onboarding, once. If you would rather not touch DNS at all, a contest can run on a laurelvoting.com subdomain instead — but then the SEO is ours, not yours, and we will tell you that rather than let you find out in a year.
Who processes payments?
▸
Stripe, on our account. We are the merchant of record for your subscription and for every sponsorship a business buys, which means the buyer checks out on Stripe’s own hosted page, no card number ever reaches your systems or ours, and the PCI burden is not yours. Your share of self-serve sponsorship revenue is reconciled onto a statement you can download and paid out by bank transfer. That transfer is made by a person on our side today, not by an automated payout API — it is reliable, it is not instant.
What about vote fraud?
▸
Every submission is scored as it arrives — shared devices, address and subnet velocity, disposable and sequentially generated email addresses, bot user agents, implausibly fast completion — and anything that looks wrong is flagged, clustered and explained to you in plain language, with a warning when a flagged cluster is bigger than the margin in that category. What Laurel will not do is quietly reject a vote. A false positive is a reader who thinks your contest is rigged, so only a person disqualifies anything, and the database itself refuses to change a vote unless the record of who did it is written in the same breath. Voting resets at midnight in your timezone, and running tallies are never public.
Do we need a sales team?
▸
No, and the storefront is built on the assumption that you do not have one. A local business finds its category, picks a placement, pays by card and uploads its own artwork with nobody from your side involved — at two in the morning, if that is when they get to it. There is one deliberate human step: the creative does not go live until someone on your team approves it, because you should not be the last to know what is running under your masthead. If you do have a rep, an attribution link credits them and changes the split.
Can we migrate from our current platform?
▸
Partly, and here is the line. Your business list and your category structure come across as CSV — forgiving headers, a template to start from, and a preview showing what each row will do before anything is written. What you cannot bring across yet is past winners or past vote totals: there is no historical results import, so your first season on Laurel starts the archive fresh and the multi-year win history builds from there. If prior years matter to you, raise it on the call — it is on the roadmap and it is not built.