Vela

Name: Vela
Brand: Vela

AI Native

100+ AI tools built for ecommerce in one platform

Est 2026|Raised $500K|10 Ref Customers

LinkedIn 6K|Web traffic 3K|FTEs 8|HQ San Francisco, California, US

MarketsScheduling Automation Executive Productivity & Scheduling

01Competitive Landscape

Narrative analysis

- Calendly versus Vela: Calendly provides a mature, link-based scheduling workflow with visible pricing and broad market adoption; it is likely to be preferred where predictable, self-serve booking flows are adequate. Vela targets scenarios where negotiation, context, and email-native workflows are more important. - Microsoft Bookings versus Vela: For organizations standardized on Microsoft 365, Bookings is often an included procurement option and can be attractive for procurement simplicity. Vela may be an option where organizations require agentic outreach and negotiation rather than a booking page. - Motion/Reclaim versus Vela: Motion and Reclaim place more emphasis on optimizing an individual’s or team’s calendar holistically (tasks, deep work, and time-blocking). Vela is more narrowly focused on coordinating meetings with external human participants. Competitor sources: - Microsoft 365 business plans: Official Microsoft product and pricing pages - Reclaim.ai: Official vendor product and pricing pages

	Vela	Calendly	Motion
Starting Price	Not publicly listed (demo-led)	Published tiers including Free + paid tiers	Published pricing (free trial; paid tiers on site)
Best For	High-ambiguity, high-touch, multi-party coordination via natural language and messaging channels	Structured scheduling flows, booking links, teams needing routing rules	Individuals and teams seeking AI-planned schedules (tasks + meetings)
Key Strength	Negotiation-style scheduling without links; multi-channel outreach (email/SMS/WhatsApp)	Mature scheduling rules, widespread adoption, transparent pricing and procurement artifacts	Auto-scheduling combined with task/time-blocking features for personal productivity
Key Weakness	Limited independent reviews; unclear pricing; messaging compliance obligations fall on customers	Link-based model may be less suitable for complex, negotiation-style scheduling	Some users report concerns about pricing changes and complexity (varies by user community)

01Competitive Landscape

Narrative analysis

Calendly versus Vela: Calendly provides a mature, link-based scheduling workflow with visible pricing and broad market adoption; it is likely to be preferred where predictable, self-serve booking flows are adequate. Vela targets scenarios where negotiation, context, and email-native workflows are more important.
Microsoft Bookings versus Vela: For organizations standardized on Microsoft 365, Bookings is often an included procurement option and can be attractive for procurement simplicity. Vela may be an option where organizations require agentic outreach and negotiation rather than a booking page.
Motion/Reclaim versus Vela: Motion and Reclaim place more emphasis on optimizing an individual’s or team’s calendar holistically (tasks, deep work, and time-blocking). Vela is more narrowly focused on coordinating meetings with external human participants.

Competitor sources:

Microsoft 365 business plans: Official Microsoft product and pricing pages
Reclaim.ai: Official vendor product and pricing pages

	Vela	Calendly	Motion
Starting Price	Not publicly listed (demo-led)	Published tiers including Free + paid tiers	Published pricing (free trial; paid tiers on site)
Best For	High-ambiguity, high-touch, multi-party coordination via natural language and messaging channels	Structured scheduling flows, booking links, teams needing routing rules	Individuals and teams seeking AI-planned schedules (tasks + meetings)
Key Strength	Negotiation-style scheduling without links; multi-channel outreach (email/SMS/WhatsApp)	Mature scheduling rules, widespread adoption, transparent pricing and procurement artifacts	Auto-scheduling combined with task/time-blocking features for personal productivity
Key Weakness	Limited independent reviews; unclear pricing; messaging compliance obligations fall on customers	Link-based model may be less suitable for complex, negotiation-style scheduling	Some users report concerns about pricing changes and complexity (varies by user community)