One product. One builder. Paid for by couples.

I. The operation

A solo, bootstrapped operation.

Kaiplan is built and maintained by one person. Not a startup with a runway and a growth team, not a PE-backed rollup adding tools to a marketplace. One engineer, one product, funded by the couples who use it. That is not a caveat. It is the point.

Most wedding tools are free because vendors pay for the placements you see inside them. That model means the platform earns from the vendors, not the couples, which means every recommendation is shaped by who is paying. Kaiplan earns from couples directly. The pricing is on the page. The features are the product. There is no ad inventory to sell.

I read every customer complaint personally. Every support email, every bug report, every piece of feedback lands in my inbox and I respond to it. That is not a PR commitment — it is just how a one-person product works. You are not writing into a ticket queue; you are writing to the person who will fix it.

II. Bug fixes

A 24-hour bug-fix promise.

If you find a bug that breaks your workflow — something that stops you from saving a guest, updating a budget line, or generating a seating assignment — write to hello@kaiplan.app. I commit to a fix within 24 hours for anything that blocks core planning work. Not a workaround, not a timeline — a fix.

Kaiplan is a paid product. If it does not work, you should not be paying for it. The 24-hour window reflects that. Non-blocking improvements and feature work move at a different cadence, but broken core features do not wait.

III. How to reach me

Email and LinkedIn.

For support, feedback, or anything about the product: hello@kaiplan.app. I respond personally and I keep every conversation in context — if you wrote last month, I remember it.

If you want to see what else I am building or follow the product publicly: linkedin.com/in/angelcampa1.