Welcome to the Tukt blog
This is the first post, so it should probably say what the blog is for.
Product pages are bad at detail. They have to be short, they have to be confident, and they compress everything interesting into a phrase. Ours says Tukt is property management software with end-to-end operations functionality, which is accurate and tells you almost nothing about what that took to decide.
This is where the detail goes.
What we expect to write about
Operations. The parts of running a property that happen after the booking is confirmed — turnovers, cleaners, maintenance, the handful of things that go wrong at the worst possible time. This is the part most software treats as somebody else's problem, and it is the part we find most interesting.
Regulation, jurisdiction by jurisdiction. Short-term rental rules differ by country, by state, and sometimes by council, and they change without much warning. We have to encode them precisely enough that software can act on them, which means reading them closely. Writing that up seems more useful than keeping it in a spec.
The reasoning behind the build. Why money is integer cents everywhere. Why a missing compliance rule is a hard error instead of a quiet skip. Why we think "end-to-end" means covering the whole lifecycle rather than removing people from it. Decisions like these are more interesting with the argument attached, and the argument is usually where the useful part is.
Who it is for
Mostly people who run properties, and people who build software for them. If you have ever reconciled a payout by hand at eleven at night, or explained a local rule to a system that had no way to represent it, you are the audience.
We would rather be specific and occasionally wrong than vague and safe. If we get something wrong about your market, tell us — info@tukt.com.au. Corrections are welcome and will be made in public.