The work spans more than a website.
A sales page gets someone to an event. The next steps involve registration details, relationship history, email, and access to the right tools or course. Those handoffs are part of the software work.
Vayu's setup includes Vayu Flow and Vayu Breathe, sales sites, TwentyCRM for relationship management, Formbricks for forms and surveys, and automations around Luma events and Loops email.
Give each tool a clear job.
| Need | Tool | How it fits |
|---|---|---|
| Customer relationships | TwentyCRM | Self-hosted records and event context. |
| Forms and surveys | Formbricks | A Vayu project within a shared self-hosted service. |
| Registration and email | Luma, n8n and Loops | Managed services connected through hosted automation. |
| Custom tools | Vayu Flow and Vayu Breathe | Product experiences with supporting websites. Breathe also runs as a desktop app. |
| Sales pages | Vayu microsites | Hosting chosen per site, including VPS and Vercel. |
Two connected paths after registration
For mapped events, a custom service adds or updates the registrant's record and event context. It matches existing contacts by email, rather than treating every registration as a new person.
A separate workflow handles registration information in Loops. For configured cohorts, it also adds the participant to the course roster, sends the welcome email and arranges the remaining calendar invitations.
These are separate paths. The evidence does not establish that every registration goes through Twenty before reaching Loops. Event mapping, eligibility checks and the configured cohort determine what runs.
Test the handoff people actually receive.
The September 21 October-cohort rehearsal used a signed test registration. It created the course roster entry, delivered the Loops welcome email and delivered the calendar invitation. The test records were then removed.
The rehearsal exercised the custom onboarding workflow. It did not include a real paid Luma checkout. It also did not create a new marketing contact in Loops, which is a separate step from sending a transactional welcome email.
The result is a connected operating setup.
Vayu has business tools and custom applications that can work together across hosting providers. The value to assess is the reliability of those handoffs and the manual work they replace, alongside their full running cost.
No quantified time saving, revenue lift or net cost saving is claimed here. Personal hosting also creates an ownership and handover question: who controls the accounts, data, backups and future maintenance needs to be explicit.
Bring one recurring handoff.
The $495 Software & Workflow Assessment examines one recurring problem, compares up to three researched options, and gives you a written recommendation with costs and maintenance responsibilities. Implementation is quoted separately.