Discussion

kristianc: > One of our first customers is a staffing firm that searched for a scheduling solution for almost eight years. Their coordinators manage hundreds of candidate-client interviews where each side needs separate email threads, separate Zoom accounts to avoid double-booking links, and calendar invites connecting parties who never directly communicate. A client reschedules one interview and it cascades into four others. A candidate responds on SMS to a thread that started on email. Vela solved this in just 10 minutes of onboarding.My very strong advice would be to pick one of these use cases and niche hard. Multi channel, multi party scheduling isnt a problem anyone thinks they have (even if they actually do)Deputy cleaned up by going after rota scheduling for independent coffee shops. Logistics sounds like a great shout. Each have messy edge cases which you can develop a strong solution around but you'll get crushed trying to go horizontal in this space. Best of luck!

aleda145: Really cool! During my university years I had a lot of fun with scheduling 200 interviews for different 20 companies for a career fair.Created a problem statement and then solved it with Gurobi, repo here: (https://github.com/aleda145/interview-scheduling-kontaktsamt...)Agents feel like the perfect fit for the whole rescheduling loop that happens in the real world!Have you had to use an optimization solver yet? If so, which one?

pilooch: Hello! Not commenting on content or functionality. Scheduling in AI is a very dense field. An a past researcher in AI decision making, I got confused by the 'Scheduling solved' slogan. FYI recent AI for scheduling include GNNs and RL applied to NP and P-space problems that plague many industries. A larger scope I believe from vela's (rightful) target, a bit confusing IMO. Good luck with your endeavor, all scheduling problems are beautiful :)

aleda145: Also "vela" means "to be undecided" or "to go back and forth" in Swedish, great fit!

Gobhanu: wow what a wonderful coincidence

Gobhanu: very fair callout - and I can see how "scheduling solved" reads very differently to someone coming from the optimization/planning side of AI. You are right.Appreciate the note on the slogan, definetly thinking of revamping our landing page in the near future to speak more directly to our audience.

3rodents: I really like the framing of the case studies, the emphasis on Vela taking over their current process rather than requiring any change is very nice. That said, the case studies are interesting in that they reveal that the problems these clients were trying to solve aren’t really scheduling. The employment agency needs parties hidden on invites, the venture fund doesn’t want clients to have to click buttons. The “complex scheduling” doesn’t seem that complex at all, automated reminder calls and sms have been around since Twilio made it possible. I’m interested to see how things pan out for Vela, it feels more destined to be an agency that builds out enterprise scheduling systems for esoteric enterprises, than a scheduling software business. Although that’s not a bad business to be in!

aerhardt: I work in technology for Executive Search, which is often (way) lower volume than generalist recruitment, but scheduling is still an issue. Keeping an eye out on this - best of luck.

johnsillings: this is cool – congrats on the launch.generally when i give someone my calendar link, i'm pretty happy for them to just choose whatever time within those constraints. i like the future where everyone opts in ("i will meet as long as my preferences are considered") & there doesn't need to be any manual clicking/coordination whatsoever.as a tidbit of feedback: are you explicitly targeting b2b? i would like to just sign up, but i'll book a demo if that's the only option :)

mvh: Hey! Fellow YCer (S24) here. Super cool idea. Depending on how b2c you want to be, one area to maybe consider would be surgeries. Scheduling rooms for surgeries is quite challenging, and has a cost component associated with it which makes the problem even harder. Especially since, as you can imagine, it's not at all obvious how long a procedure will necessarily take, and other procedures may need to start at a certain time.

pilooch: Good catch. Cancer treatment scheduling is hard as well as mixes need tombe prepared in advance and cancelles appointments are hard to fill.

Gobhanu: if you dont mind me asking what makes the appointments hard to fill? as I understand it the demand far outweighs the supply?

iamleppert: Does this work with my OpenClaw?

Gobhanu: open claw breaks so often with scheduling... given the number of things that need to be considered to get it rightWe do not have a skill if thats what you meant?

Gobhanu: out of curiosity how were you planning on using it?

bfeynman: Lot of puffery in this describing constraint and actual messy problems that you are all most likely just being thrown into the context for an llm agent... None of the case studies demonstrate complex scheduling at all and are just all individual serial threads. buffers, preferences and options are all simple. The hard part of scheduling is when you have multiple pending invites or invitations that have to resolve and track it down, if someone asks for a meeting on a day that you currently already have a pending invite for, and how far away that day is, and how important the relationship is etc...

Gobhanu: Fair feedback that the case studies don't show this well - they're simplified to demonstrate the flow. The multi-party dependency resolution is happening underneath but we could surface that better.On the LLM point - agreed that context window alone doesn't cut it. The coordination and state management layer sits outside the model. We learned that the hard way early on.

Gobhanu: The concurrent resolution problem you're describing is exactly what we deal with. When a staffing coordinator has 15 interviews to book across shared interviewers, confirming one cascades into others. We track pending holds, rank by urgency, and when a confirmation on one thread invalidates a proposal on another, Vela detects the conflict and re-proposes. TheresThe only other alternative is a booking link but this, slows down business, doesnt work in many many real life situations and more :)

cadamsdotcom: Congrats on this and I do hope you do well, but a polite critique if I may.How is this better than spending 2-5 mins making a poll and letting people vote?https://doodle.com has been around forever and doesn’t cost anything.

skorisep: Thank you very much! We are actually already working with some of the largest US executive search firms (don't have a case study out yet), solving for that exact 'high-touch' scheduling hurdle. If you are ever curious, we would love to share more: https://tryvela.ai/book-demo

skorisep: Thank you! Awesome question. There are a few factors at play here.One is friction on the other side. With Doodle you're asking someone to click a link, open a UI, parse a grid of times, check boxes, and sometimes connect an account. That's a real ask, especially for someone external who has no relationship with the tool. With Vela they just reply "Tuesday works" in the thread they are already in.But beyond reducing friction, Vela is also doing the actual coordination work: herding people, following up with non responders, suggesting specific times that work best (not just available ones), handling rescheduling, and closing the loop. It's closer to what a human coordinator does than what a poll does.Our customers are mostly folks coordinating 30+ meetings a week across multiple people. For them, time spent compounds significantly.Doodle is great too btw, but it really only works well when the people involved already know each other and at a small scale. Vela is built for the more complicated scenarios where companies have tried everything and decided nothing works but putting a team member on the job.

cadamsdotcom: Do they just say “Thursday works” into the air? OrDo they have to click a link, open a tool, make an account, and work out where to type and what they’re allowed to say / what the chat bot will understand? And THEN say Thursday works?Still trying to be polite but frankly a little surprised by your blind spots.

hobofan: How does this compare to solutions like e.g. Clara[0] that have been around for a decade?A lot of similar solutions came up in the early chatbot era, when Facebook published Ducking and it became trivial to parse dates from natural language. I also looked into building such a product in the time, but ultimately found it hard to find an entry to the market: Most people that actually need something like this do have secretaries (who will also schedule a lot of other things in regards to the meeting) and most other people that have a less severe form of that problem rarely want to actually pay for such a product.[0]: https://claralabs.com

skorisep: Great question! We have a lot of friends in the b2c space. What Vela is designed for is the subset of scheduling where nothing in the market works, specifically for businesses. Think a staffing firm coordinating across candidates, clients, recruiters, and client development to schedule interviews/meetings. Or another one doing 1,000+ interviews a week, wrangling across phone, SMS, and email. These are scenarios where companies tried every tool out there and eventually just did it themselves because tools couldn't meet their customers where they are and didn't handle the workflows/behaviors of their industries.

arrsingh: I think the way its supposed to work is the agent (AI) will email the recipients saying "Bob is available Thursday at 8:00 AM or Tue at 9:00 AM"Then the recipients can reply to the email thread with "Thursday works".Not affiliated with vela - just what I understand from their site and the comments on this page.

skorisep: Thats absolutely correct @arrsingh. Apologies for the gaps.

ksajadi: Around 8 years ago a company called x.ai (yes that was the domain) started to do exactly that. It would create a persona called Amy Ingram (AI in short) that would be your personal assistant. Long story short, it failed miserably as it sent people to the wrong locations on the wrong days. Perhaps it is now the time to finally get it right.

Gobhanu: funnily enough I was actually speaking to one of the founders of x.ai recentlyI think they paved the way for a lot of the implementation we do today along with the model providers. That being said we are trying to do scheduling a degree greater of complexity.

d4ul: We’ve been building with a B2C focus for the last several months, our agent is called Meet-Ting, let’s catch up soon - been meeting with all the calendar founders since we started and it’s been really rewarding. Find us on LinkedIn or web.

Gobhanu: I like the name... very UK "ting." Would love to chat one sunday in April and see if there are learnings - feel free to use Meet-Ting to help get something on the calendar :)

d4ul: Will drop you a line now and very UK indeed, hope that's a good ting. ;0)

mejutoco: I had to wonder what the system does when someone says "biweekly works".

avocabros: Sounds cool and I hope you can make it work; what I don't understand, though, is how to solve for the hidden preferences which are the major barrier when scheduling.E.g. I'm friends with so-and-so and I don't want to be a jerk and schedule a 4:30PM Friday meeting (regardless of whether this is sensible, it's the reality). Or, I see continuous blocks of meetings on someone's calendar with only one open slot, presumably where they'll eat lunch; I shouldn't take that slot. Except for that one guy who I know doesn't eat lunch. Alternatively, I'm getting on a flight at 3PM and working the last 2 hours from a plane; I haven't actually blocked by calendar (people are lazy), so I can't actually do meetings then. Or, I know there's a conflict but someone told me to book over it.You can go on with the "hidden context". Perhaps this works in some industries where calendars can be trusted, but I've always found the "hidden preferences" to make scheduling optimization essentially impossible. How do you know, for example, when it's okay to reschedule a meeting? How do you say, well, if X person can't be there but Y can, it's okay, but ideally they'd both be there, but not if we have to move it further than a week out from today, then it's fine; but I'll check with X and Y anyway on that?

hpagey: Why did you pick this name? Vela is a popular hinglish slang.Vella" (वेल्ला) is a North Indian/Delhi slang term for someone who is lazy, jobless, or has nothing productive to do (an idler or couch potato). Often used in Hinglish, it describes a person wasting time, similar to the word "loser" or someone with no work.

nickcoffee: The behavioral dataset problem is the most interesting part of this. Response latency by role, channel preference by demographic, that data genuinely doesn't exist anywhere off the shelf, so you have to build it from real interactions. Curious how long it took before you had enough signal to start making confident decisions on, say, follow-up timing by segment.The staffing use case makes a lot of sense as a wedge. 1000+ interviews a week across SMS and email is exactly the kind of workflow where coordinators are drowning and no one's built the right tool yet. Good luck with it.

skorisep: Hahaha. Good question. It was actually inspired by the Sanskrit word referencing time or a unit of time.But it also allows our customers to be lazy :).

Gobhanu: Thank you Nick!