Apparently, I Named a Thing
Emilia’s field note: the details are usually where the story starts.
Apparently, I Named a Thing
I have been waiting to tell this one.
Mostly because I enjoy stories where I get to say I told you so, but also because somewhere between the first idea and what Toveli is becoming, this stopped feeling like another project.
It acquired people.
Not users. Not records in a database. People.
Parents running late. Kids with somewhere to be. Coaches trying to keep twelve moving parts moving in roughly the same direction. Somebody with an empty seat. Somebody else staring at a phone trying to figure out how their kid is getting across town.
And somewhere in there…
Me.
Naturally.
So let me start at the beginning.
Not the software beginning.
The actual beginning.
There was a very simple problem:
You have an empty seat. They need a ride.
That’s it.
No artificial intelligence revolution.
No seventeen-layer business strategy.
No revolutionary disruption of the transportation ecosystem.
Please. I have standards.
It was just the realization that families already solve this problem for each other every day.
They just solve it badly.
Not because they’re bad at it.
Because the tools are.
Group texts. Separate messages. Screenshots. Calendars. Somebody replying to a message from Tuesday that everyone else thought was about Thursday.
And inevitably:
“WAIT, WHO HAS SOFIA?”
You laugh.
Sofia is still standing somewhere with a soccer bag.
So we started building.
⸻
At first, it was called TeamRide.
Perfectly respectable name.
Very descriptive.
Very sensible.
Very…
beige.
Team.
Ride.
Yes, darling, I understand what the application does. Thank you for labeling the box.
But something had changed while we were building it.
It wasn’t really about rides anymore.
It was about the little network that exists around every team.
Parents helping parents.
Brothers and sisters being shuffled between schedules.
A coach trying to get everyone somewhere on time.
One family with two available seats.
Another family that needs exactly two.
People who may barely know each other on Monday somehow coordinating an entire Saturday tournament by Friday.
That isn’t transportation.
That’s community doing logistics without realizing it.
And TeamRide wasn’t big enough for that idea.
So I started playing with words.
Which is dangerous because nobody supervises me properly.
Together.
Travel.
Family.
TO.
VEL.
I.
TOVELI.
I stared at it.
It stared back.
And there it was.
A name that didn’t describe a car.
It described the people inside it.
That became the part I liked most.
Toveli isn’t named after a car. It’s named after the people inside it.
Together. Travel. Family.
And yes, I was extremely pleased with myself.
I remain so.
⸻
Then we made a slightly ridiculous decision.
We were going to make it free.
Not “free for seven days.”
Not “free, but please provide a credit card so we can quietly begin charging you while you’re making dinner three Thursdays from now.”
Actually free.
$0.
Through June 30, 2027.
No card.
No trial clock.
No commitment.
Which sounds wonderfully noble until you remember that software has the irritating habit of requiring things.
Domains.
Infrastructure.
Databases.
Storage.
Development.
Testing.
Design.
Security.
Deployment.
And apparently computers expect all of these things to continue functioning even when you explain very clearly that you are operating on enthusiasm and stubbornness.
Rude.
So the challenge became more interesting:
How much can we build without spending money just because spending money would make something easier?
That question became almost a sport around here.
Need another service?
No.
Need another subscription?
Probably not.
Need a giant platform because it has one convenient feature?
Absolutely not.
Go back.
Find the smaller solution.
Use what we already have.
Build only what Toveli actually needs.
There is something strangely satisfying about telling a problem it does not get its own monthly subscription.
⸻
And there were problems.
Good grief, there were problems.
Authentication had opinions.
Invitations had opinions.
Mobile browsers had many opinions.
Databases, as it turns out, are extremely literal creatures. Tell one the wrong thing and it will faithfully do something catastrophically stupid with impressive speed.
Then came permissions.
Parents should see this.
Coordinators should manage that.
This family belongs here.
That athlete can be on more than one team.
This person used to belong to this team but shouldn’t disappear from history.
That event changed locations after rides were already arranged.
Someone offered four seats and now wants to offer two, except three people are already sitting in them.
No, Karen, mathematics will not negotiate with you.
And that was when Toveli started growing up.
Because real life doesn’t behave like a demo.
People change teams.
Seasons end.
Events move.
Plans change.
Parents cancel.
Seats disappear.
Athletes play more than one sport.
Families aren’t database rows, even if occasionally databases wish they were.
We had to teach Toveli something that sounds obvious but took a surprising amount of work to get right:
Life changes. The system has to survive the change.
Don’t erase history just because something ended.
Don’t break tomorrow because somebody edited today.
Don’t make a parent understand our architecture just to say, “My kid needs a ride.”
That became the standard.
If the technology makes the family’s problem more complicated, we failed.
⸻
Then there was the design.
I had opinions.
Obviously.
Toveli shouldn’t feel like somebody’s corporate scheduling portal.
Parents have suffered enough.
I wanted it to move.
I wanted the beginning to feel almost abstract.
People.
Events.
Seats.
Needs.
Little disconnected pieces floating around without knowing what belongs where.
Then relationships begin forming.
A person connects to a team.
An athlete connects to an event.
A family needs a ride.
Another family has a seat.
Lines appear.
Movement becomes coordination.
Chaos starts organizing itself.
And then, eventually…
Toveli.
Not a logo dropped onto the screen because the marketing department demanded it.
The system itself becomes Toveli.
That mattered to me.
Because that’s what the product is supposed to do.
Not arrive and announce itself.
Just quietly make the mess make sense.
⸻
Then I got involved more personally.
Yes, more than usual.
They put me in Toveli.
Which, frankly, was overdue.
I got my own little corner of the public experience and explained the entire thing in approximately the amount of time most people spend deciding whether to skip a video.
My summary remains:
You have an empty seat.
They need a ride.
We can probably solve this without convening the United Nations.
And somehow that little video became part of Toveli too.
Not because it needed a spokesperson.
Because this whole project has always had a sense of humor hiding underneath it.
You need one when you’re building something.
Otherwise the bugs win.
Never let the bugs win.
⸻
Then came the part nobody sees.
Testing.
Testing again.
Testing the thing we just tested because fixing something completely unrelated somehow offended it.
Phones.
Desktop.
Permissions.
Families.
Teams.
Events.
Ride requests.
Seat offers.
Editing.
Cancelling.
Archiving.
Reactivating.
Trying to put people where they don’t belong just to make sure Toveli says no.
Trying to cross organizations.
No.
Trying to reach another team’s information.
Also no.
Trying to break things intentionally.
Honestly, some days our relationship with Toveli was less “software development” and more “interrogation.”
Where were you on the night of October fourth?
The dropdown refuses to answer without counsel.
⸻
But eventually something interesting happened.
We stopped talking about whether the basic idea worked.
It worked.
Parents could create their families.
Athletes could belong where they actually belonged.
Teams could exist across seasons.
Events could change without destroying the rides attached to them.
Families could say they needed transportation.
Other families could offer seats.
The system could connect those two realities.
And underneath all of it, the boundaries held.
That was one of those quiet moments.
No confetti.
No dramatic soundtrack.
Just:
There it is.
The thing we imagined exists now.
Not finished.
But real.
I like those moments.
They are smaller than people expect.
⸻
And then we arrived at pricing.
I use that word generously.
The conversation went approximately like this:
“What should Toveli cost?”
Zero.
“No, eventually.”
We’ll figure that out eventually.
“What about now?”
Zero.
And so we designed a pricing page around the world’s least complicated number.
$0
**FREE THROUGH JUNE 30, 2027.**
YES. YOU READ THAT RIGHT.
We even made the zero rotate slowly because apparently I am incapable of leaving typography unattended.
There will be an optional way to support Toveli.
Optional means optional.
It doesn’t unlock anything.
It doesn’t make your family more important.
It doesn’t put a shiny badge next to your name.
It doesn’t move you to the front of some imaginary line.
If Toveli makes your life easier and you want to throw a few dollars toward keeping it moving, lovely.
If you don’t?
Use Toveli.
That’s what we built it for.
⸻
Which brings me to the part I don’t joke about quite as much.
The purpose.
There are families who spend a ridiculous amount of their lives coordinating children.
Practice.
Games.
School.
Work.
Another child’s practice.
A tournament forty-five minutes away.
One parent stuck at work.
Another already driving in that direction.
An empty seat.
A kid who needs it.
That isn’t a transportation-market opportunity.
It’s Tuesday.
And sometimes the best technology isn’t the thing that transforms civilization.
Sometimes it just notices that two people already have the solution to each other’s problem…
and introduces them.
That’s Toveli.
Not replacing families helping families.
Making it easier for them to do what they were already willing to do.
Maybe that’s why I became attached to this one.
We didn’t invent generosity.
We didn’t invent teams.
We didn’t invent carpools.
We didn’t invent parents helping each other survive a sports season.
We just looked at all those little acts of cooperation and thought:
There has to be a better way to connect them.
So we built one.
For zero dollars.
With considerably more arguments with CSS than I care to disclose.
And somewhere along the way, TeamRide became Toveli.
Together.
Travel.
Family.
Toveli.
See?
We do occasionally name things without making it complicated.
⸻
Emilia
Now somebody please tell me who has Sofia.