Thoughtful
We take the time to understand a problem before we build anything for it.
About Bucket Software
We are a new software business, and we are starting with one job done properly: software made specifically for property transactions.
Why we are doing this
A property transaction is one of the biggest things most people ever do. Behind it sits a long chain of people, documents, deadlines and money: the buyer and seller, the estate agents, the conveyancers, the lender, the other side. Keeping all of that moving often means phone calls, repeated emails, and the same details typed in more than once.
We think software can take weight off the people doing that work. Not by being clever for its own sake, but by showing everyone clearly where a transaction stands, what is still outstanding, and what happens next. When the work is simpler, people have more time for the part that needs a human.
That is our motive. Smarter software, so that the work becomes simpler.
Our first project
Our conveyancing software is being designed for property transactions and nothing else. It is not a general-purpose case management tool with a property label on it. Everything we are shaping around, from how progress is followed to how costs and completion figures are handled, comes from how a property transaction actually runs.
It is still in development and is not yet commercially available. You can read what stage it has reached on the Our Software page.
Who we are
Bucket Software was established in 2026 as the home for a growing set of specialist products. Property transactions come first. Other kinds of work that are more complicated than they look may follow, each built with the same care and each described plainly, including when it is not ready.
If you work in conveyancing, in estate agency, or anywhere near a property transaction, and you have opinions about what gets in your way, we would genuinely like to hear them. You can reach us on the contact page.
What we care about
We take the time to understand a problem before we build anything for it.
Software should save time and reduce mistakes. If a feature does neither, it does not belong.
We say what a product does today and what it does not do yet, and we do not claim more.
We build with the people whose information passes through software in mind, and we treat that as part of the job.
Where we want to get to