Management App
Onera
Built an all-in-one management platform for operators: property managers, sports managers, general teams. One system. No context switching.
View buildThe idea
Onera Management is an all in one management platform built for people running operations. Property managers, sports managers, general operators. The goal is simple. Track work, manage communication and keep everything in one place without needing five different tools. It was built on a clear belief. Most tools are designed around industries. This one is built around how managers actually work, regardless of industry.
The problem
Most management tools are powerful, but they come with friction. • Too many features upfront • Steep learning curve • Multiple tools needed to do one job • Constant context switching People waste time learning tools instead of doing the work. The gap is not capability. It is usability. Tools assume complexity is required. In reality, most managers need a clean system that covers the basics well.
The strategy
The core idea was to strip things back. • Focus on what all managers have in common • Combine tracking, communication and structure into one system • Remove unnecessary layers • Keep the experience direct Instead of building deeper into one niche, the approach was to build a strong base layer that works across industries.
The build
Stack • Next.js with TypeScript • Supabase database • Supabase Auth The system is multi tenant by design. Each organisation operates in its own space while sharing the same infrastructure. Data flows through standard GET and POST patterns, keeping interactions predictable and easy to extend. At a high level: • Frontend handles user interaction and state • Supabase manages auth and data • Logic is structured around core entities like tasks, users and projects • Async behaviour is handled on the client side where needed, keeping the experience responsive. The structure is intentionally simple. That makes it easier to scale without rewriting the foundation.
The product in use
At its core, the system is about flow. A manager can: • Create and track work • Assign responsibility • Communicate within context • See what is happening without chasing updates The difference is not in adding more features. It is in removing friction between actions. Everything sits in one place, so users are not jumping between tools to get a full picture.
The experience
The UX is built around speed and clarity. • Reduced steps to complete actions • Minimal setup required • Clean interface with no clutter • Mobile friendly from the start What was intentionally removed: • Overloaded dashboards • Complex onboarding flows • Feature heavy menus What a user notices immediately is how quickly they can start. There is no long learning phase.
The challenges
This was not a smooth build. Architecture had to be revisited multiple times. What seems simple on the surface becomes complex once you introduce: • Multi tenant structure • Real time updates • Clean data relationships • Scalable patterns Getting the balance right between flexibility and simplicity took the most time. Several parts were rebuilt to avoid cornering the system into something rigid early on.
Current state & feedback
The product is live and in use. Early feedback is clear: • It is useful • It needs more depth in certain areas What is working: • Core flows • Simplicity • Ease of use What needs work: • Additional layers for more advanced use cases • Refinement of certain workflows This is expected at this stage. The foundation is the hard part, and that is in place.
Why this matters
This project shows more than design or development. It shows: • System thinking • Ability to simplify complex problems • Willingness to rebuild until the structure is right • Understanding of how software is actually used day to day For a founder or technical lead, this matters more than surface level polish. It proves you can take an idea, structure it properly and bring it to life in a way that people can actually use.
Where this goes
Onera is not tied to one industry. That opens up scale: • Property management • Sports operations • Small business teams • Agencies The long term direction is clear. Build a strong core, then layer depth where needed without breaking simplicity. If done right, it becomes a system people rely on daily, not another tool they abandon.