Web platforms
The product people log into, and the tools behind it.
We build customer portals, dashboards, marketplaces, and administrative tools, with roles, permissions, and sensitive data requirements defined early in delivery.
What you get.
- A web product real users can log into
- Admin and back-office tools aligned with your team's workflow
- Permissions designed before the screens
- The repository, from the first commit
How it works.
01
Write down the users and the records
Who logs in, what they are allowed to see, and what happens when they should not. That page comes before visual design.
02
Ship the smallest useful surface
We prioritize the smallest useful workflow, then expand the product based on agreed needs and user feedback.
03
Hand it over running
Logging, access reviews, and an operations guide. Your team can keep adding screens without calling us for every change.
Fit.
These criteria help determine whether the engagement model matches your requirements.
This is a fit when
- A customer portal, marketplace, or dashboard that has to exist in months
- Admin tools that are currently a spreadsheet and a prayer
- A founding team that will live in the product after launch
A poor fit when
- A brochure site with no accounts and no data
- A theme you could buy and never touch again
- A programme that needs a large team assembled from scratch
Products we run.
Averil and LobeStack are both web products we own and still operate. The write-ups include the screens we should not have built first.
Questions.
How long does a project take?
Timing depends on the scope, existing systems, integrations, and review requirements. We use an initial assessment to define the delivery stages and provide a more reliable estimate before the main build begins.
Who owns the code?
Client work is maintained in a repository the client can access. Source-code ownership, third-party components, and any licensing terms are documented in the engagement agreement.
How many clients do you take at once?
About three partner products a year. We limit concurrent client work so the proposed team can remain involved throughout the engagement. Current availability is confirmed during the initial conversation.
Plan a product build.
We aim to reply within two working days. Email info@techsity.comif you would rather provide project details directly.