ORIGIN · 由来 / PHILOSOPHY · 哲学
Spidee is built by a small remote team split between Taipei and Kyoto. We use it ourselves, we wrote it for our friends, and we want it to still feel right ten years from now. This page is about why it exists — and what it doesn't intend to become.
A few years ago, a handful of us spent New Year's in Kyoto. Lodging, an izakaya night, a taxi back from Arashiyama — each receipt was small. Together they were chaos. We sat in an Airbnb near Nishiki Market trying to do the math in a Google Sheet, and spent an hour arguing — "who paid for the matcha?" "Was 580 including tax?" Somebody accidentally overwrote a row.
That night we started asking ourselves why splitting bills, in 2024, was still this brittle. We didn't want another app full of notifications and "power-user" pressure. We wanted a quiet ledger — something that remembers who paid, who owes, when it's settled, and then gets out of the way. Spidee is what came out of that conversation.
Spidee has four design rules:
One — don't interrupt. No push notifications, no red dots, no streaks.
Two — don't upsell. There is no "upgrade to Pro" modal waiting to ambush you.
Three — don't track behaviour to sell data. We don't even want the analytics dashboards ourselves, let alone sell your spending to a third party.
Four — get out of the way once you're done. Logging an expense should take about ten seconds. We won't force you through five required fields just to record a coffee.
Spidee is built by a small remote team across Taipei and Kyoto. No office, no funding, no "growth metrics" dashboard — just a few people who care about quiet tools, a Slack workspace, and an occasional online brainstorm.
Everyone on the team has a day job; we treat Spidee as a slow side project we want to keep building for a long time. A single feature might iterate for two months before shipping, because we care more about "does this hold up for ten years" than "can we ship by next week."
You won't find our headshots or bios on this page. The product isn't about us — it's about itself. But every message, every bug report, lands in front of real people who read and reply.
Bug reports, feature requests, business inquiries, or just something you want to say to the team — all welcome via the contact page. We check the inbox roughly once a day. Most messages get a reply within a day or two.