We build products.
SimpleTools is an independent product company building software for consumer and business markets.
We find problems worth solving, build around real behaviour, and improve products through use.
Built around problems.
We don't start with software categories.
We start with problems people already have.
A private space for two.
Communication built around closeness, expression, and shared experiences.
Turn Todos into Ws.
Productivity built around commitment, execution, and completion.
Know who's actually at work.
Attendance verification based on real-world presence.
Operational clarity for physical businesses.
Software for managing the work behind the business.
• Private Duo Space“A little space that belongs to two people.”
Handwritten note & pinned memory · Sub-150ms delta syncStart with the problem.
We look for friction in the way people work, communicate, decide, and get things done.
We study the behaviour around it.
Then we build the smallest system that can solve it well.
Observe
We look for friction in the way people work, communicate, decide, and get things done.
Build
We build the smallest, most focused system that can solve the underlying problem well.
Measure
We measure genuine behaviour, retention, and utility in daily use—not vanity downloads.
Improve
What earns traction gets invested in and refined. What does not gets changed or stopped.
Simple is not the absence of complexity.
It is what remains after complexity has been understood.
A product can have sophisticated technology, complex infrastructure, and powerful capabilities.
The person using it should experience none of the unnecessary complexity.
“The complexity belongs in the system.
The simplicity belongs in the experience.”
The Complexity Collapse
Toggle the switch to watch high-entropy system mechanics collapse into a single human action.
One Clean Action
No menus. No cognitive friction. The system absorbed 18 background variables to present exactly what you need.
What we learn stays with us.
Every product adds to our technology, product systems, distribution, research, and operating knowledge.
The next product starts with more than the last one did.
Technology compounds.
Shared infrastructure, reusable client architectures, offline-first sync protocols, and hardware bridge firmware power successive tools faster.
Knowledge compounds.
Behavioural observations, operational insights, and interface psychology uncovered in one problem inform the architecture of the next.
Distribution compounds.
Audience trust, community momentum, operator relationships, and cohort feedback loops expand with each release.
That is how a small team can build more over time.
Build small. Learn fast.
We launch early enough to learn from real users and stay close enough to the product to understand what is actually working.
We measure behaviour, retention, conversion, and economics—not just downloads.
What earns traction gets more investment.
When a tool proves it solves real friction with high retention and healthy economics, we deepen engineering, expand platform reach, and pour energy into its future.
What doesn't gets changed or stopped.
We refuse to pour resources into artificial engagement loops or unviable features. If real usage does not substantiate the hypothesis, we adapt immediately or halt development.
Small team. Long horizon.
SimpleTools is deliberately lean.
We want fewer layers between an idea, a product, and the people using it.
That lets us move quickly, stay disciplined with capital, and spend more time on the work that matters.
We're building for the long term.
Products become businesses.
When a product develops the users, economics, and leadership to stand on its own, it should have the opportunity to do exactly that.
A product can become a company.
A company can create its own team.
And the experience can feed the next product.
Build → Grow → Spin out → Repeat
For people who want to build.
We're interested in founders, engineers, designers, researchers, and product thinkers who see problems worth solving.
As SimpleTools grows, we want to create more opportunities for good ideas to become real products.
What we're learning.
Product · Design · Technology · Human behaviour · Distribution · Economics
The Journal documents the thinking, experiments, and lessons behind the products.
Why a pressure cooker has better UX than most apps
In an era of dashboard bloat and noisy push alerts, a humble kitchen pressure cooker demonstrates the pinnacle of interface clarity. By translating complex, invisible thermodynamic states into a single, unambiguous acoustic signal, it solves the fundamental UX problem: communicating system status without overwhelming human attention.
The tiny bumps that make your keyboard easier to use
Two barely perceptible ridges on the F and J keys anchor millions of typists without requiring a single glance. When software designers disregard these hard-won conventions in pursuit of aesthetic novelty, they break muscle memory and force users to relearn what should be instinctive.
Why good software gets out of your way
The most profound tools in human history do not demand adoration; they dissolve into the task at hand. When software shifts from an invisible cognitive prosthetic to a self-aggrandizing destination competing for screen time, it ceases to be a tool and becomes an obstruction.
Get closer to what we're building.
Join the SimpleTools beta list for early access to products and experiments.