Customer and staff portals
Give each user a practical place to see the records and actions relevant to their role, with access rules agreed before development.
Spreadsheets and off-the-shelf tools have their place. When they no longer fit, we can build a focused application around your process, your team and your customers.
A custom web application makes sense when your process needs more than a marketing website. We define the users, records, permissions and workflows before designing the interface.
Give each user a practical place to see the records and actions relevant to their role, with access rules agreed before development.
Replace a difficult spreadsheet or disconnected process with a shared interface, clear states and the reports your team actually uses.
Connect supported APIs and existing systems, document ownership of the data and plan for unavailable services or incomplete records.
The main user journeys, roles and permissions, data model, integrations, acceptance criteria and handover. The proposal should distinguish an initial release from later features and state who owns the source code, hosting accounts and ongoing maintenance responsibilities.
Projects are delivered remotely, with scope and review times agreed around your team.
Melos builds custom web applications for business workflows, customer portals and internal dashboards. The work covers user roles, data, interfaces, integrations and deployment. We define the first useful release before extending it. A browser-based application is distinct from a native iOS or Android app.
The difficult parts are often permissions, workflow states and integrations rather than the number of screens. Existing data quality, migration, reporting and audit requirements also affect scope. The proposal separates the first release, optional features and recurring infrastructure or support costs.
We agree the users and core journeys, then build in stages that your team can review with example data. External integrations and data migration are checked before the launch date is fixed. Access, deployment documentation and maintenance responsibilities form part of the handover.
These are Melos starting points for common scopes. We confirm the exact price after reviewing your pages, data, integrations and goals.
A focused first release for an internal tool, portal or connected web application.
A small first release
A connected internal or customer tool
A larger product foundation
Prices are in USD and are starting estimates, not a guaranteed quote. Third-party hosting, software, model/API usage, payment processing, directory fees and taxes are not included unless a proposal says so.
Get a scoped proposal ↗These are the areas we cover. We agree the deliverables, integrations and responsibilities for your project before work begins.
Agree the users, core tasks and boundaries of the first release.
Design screens around real work, with readable information and obvious actions.
Plan the data model, integrations and permissions the application needs.
Test the agreed journeys and document deployment, ownership and ongoing maintenance.
Take a closer look at the project and the work involved.
Yes. We first review the source, dependencies and deployment setup to understand what can be safely extended.
Code ownership, third-party licenses and access are set out in the project agreement before work starts.
A new website, a useful assistant or a process that needs fixing.
Tell us where you want to start.