Why VERA exists
The wedding was never the problem.
Keeping the whole thing in your head was.
VERA is built from professional wedding planning: complex weddings, moving information, and decisions that quietly affect each other.
The gap
The context of a wedding is scattered: inboxes, meeting notes, spreadsheets, documents, phone calls and the planner's memory. The information exists. The relationships between it do not.
Existing tools store what happened. They rarely understand what it means. A guest number changes and nothing tells you which four other things just became wrong. A supplier moves a time and the conflict only appears when someone notices it.
VERA exists to hold that context together, across the life of the wedding.
Built from the work
Twenty-five years of wedding planning, turned into a system.
VERA comes from the work of professional wedding planner Christel Winther, who has planned weddings since 2002 — independent celebrations, destination weddings and multi-day events with large vendor teams.
It starts with the part generic software misses: context. What was decided. What changed. Who owes what. What was promised. And what one change does to the rest of the wedding.
VERA does not start with generic project-management software and adapt it to weddings. It starts with the wedding.
Principles
How VERA is built.
Show the work, not the activity
A feed of everything that happened is not intelligence. VERA shows the meaning of a change, in context.
Never manufacture urgency
If nothing needs you, VERA says so. Calm is a feature, not an empty state.
Ownership is explicit
Needs You, Waiting and Promise are separate things. Software that blurs them makes the planner carry the difference.
Discretion by default
Client, vendor and guest information stays inside the planner's workspace. Nothing private appears publicly.