Product web apps / 2026
Internal product
SETR
An internal workout-tracking product connecting routine building, set-by-set logging, account access and training history.
View case studyCustom applications, internal tools and platform connections begin with the business requirement, then use the simplest technical approach that can meet it reliably.
Operational problems are rarely solved by naming a technology first. The useful questions concern who needs to do what, where information lives and which steps currently create delay or duplication.
From there, the solution may be a focused web application, a user area, a custom internal tool or a well-defined connection between existing platforms.
Technical detail is made visible where it affects scope, ownership, security or the way people use the product.
A focused release can validate the core workflow before additional functionality is added.
Setr is an internal fitness product. It demonstrates an application workflow and interface, not a delivered client integration or a measured operational saving.
Project fit
01
A digital product with a defined user task or workflow
02
A business process held together by disconnected tools or repeated data entry
03
A website or commerce platform that needs custom operational functionality
The work separates essential behaviour from later possibilities, keeping the technical solution understandable and testable.
Map users, tasks, data, systems and the current points of friction.
Set the smallest coherent scope and the technical constraints around it.
Test the interface and workflow before deeper implementation.
Develop, connect and validate the release against real use.
React and Next.js can support interactive web applications, while the data layer and authentication method depend on the requirements. An integration may use a documented API, webhooks or a controlled import; it cannot be promised until the external platform is reviewed. We consider access control, validation, failure handling and maintainability alongside interface design. Technology is selected to support the workflow, not to add complexity for its own sake.
No. A clear description of the users, task, current process and desired outcome is a useful starting point for defining the technical scope.
Potentially. The available APIs, data ownership, authentication and limitations of each platform need to be reviewed before a connection is promised.
Yes. A focused first release is often the best way to test the core workflow and learn what deserves further investment.
Start with the task people need to complete and the systems involved. We’ll help define a sensible first release.