Custom software and web applications
We design and build web applications for workflows that off-the-shelf software does not fit: internal dashboards, client portals, operations platforms, APIs and SaaS products. Authentication, roles, testing, documentation and a clear handover are part of the build from day one.
Types of applications
Custom software is worth considering when your process is a real advantage, when off-the-shelf tools force awkward workarounds, or when several systems need one place to come together.
Welcome back, Dana · Site manager
14 open · 3 awaiting approval
Approvals
HVAC repair · Building C · $2,340
Approve, reject or ask a question.
Documents
Service reports and invoices
Uploaded files stored privately, linked to each job.
Roles
Client manager · Site contact · Contractor
Each sees only their sites and actions.
Admin
Users, sites, notifications, audit log
Managed by your team, no developer needed.
Scope and deliverables
The specific scope is written down before the build. These are the elements most projects need.
Included
Users, workflows, data and integrations, turned into a written scope with assumptions and exclusions.
Framework, data model, hosting and integration approach chosen for maintainability, not novelty.
Screens designed around real tasks, tested with the people who will use them.
Sign-in, permissions by role and, where appropriate, multi-factor authentication.
Settings, users and content your team can manage without a developer.
Connections to your existing tools through APIs and webhooks. See [software integration](/services/software-integration).
Automated tests for critical behavior, plus manual testing of real workflows.
Production setup, backups, documentation and a walkthrough for your team.
Example scenarios
Fictional examples to illustrate the range of work. They are not Alaysalee clients, products or results.
Situation
A distribution business tracks orders, stock and exceptions across three tools and a spreadsheet.
What would be built
A dashboard that pulls the key data into one view, with actions for common exceptions and alerts for overdue items.
A person stays involved
Managers decide on exceptions; the dashboard only brings them to attention.
Situation
A facilities company emails clients for approvals and sends reports as attachments.
What would be built
A portal where clients see work orders, approve quotes, download reports and message the team, with role-based access per site.
A person stays involved
Approvals are made by named client users and recorded.
Situation
A training provider manages rooms, trainers and courses in shared calendars.
What would be built
A booking platform with availability rules, conflict detection and reporting.
A person stays involved
Coordinators override rules when needed, with a reason recorded.
Situation
A founder has validated an idea with a no-code prototype and needs a real product foundation.
What would be built
A multi-tenant application with sign-up, roles, admin tooling and a billing-provider-ready structure.
A person stays involved
The founder prioritizes features at each increment.
Engagement approach
Projects are delivered in increments against a written scope, so you see working software early and can adjust priorities.
We meet the people involved, map the workflow and data, and agree what success looks like.
You receive a written scope with deliverables, exclusions, assumptions and a custom quote.
Key screens and the data model are designed and reviewed with you before building.
Working software is delivered in stages, with automated tests and regular demos.
Real workflows are tested, production is set up with backups, and the launch is planned.
Documentation, a walkthrough and source code, with optional ongoing support.
Trust, security and oversight
Set out in the contract. Our standard approach is that you receive the source code and documentation for the work we build for you.
Established frameworks, readable code, automated tests and written documentation, so you are not dependent on us.
Input validation, secure authentication, role checks, dependency updates and secrets kept out of code.
Optional support for fixes, updates and improvements, agreed separately with clear terms.
Fit
Readiness
It depends on the number of user roles, workflows and integrations. A focused internal tool is a much smaller project than a multi-tenant product. We estimate after discovery and deliver in increments so you see progress early.
Every project is custom quoted from a written scope, because cost depends on what is being built and integrated. We do not publish standard prices. A discovery conversation is free and without obligation.
Ownership is set out in the contract for each project. Our standard approach is that you receive the source code and documentation for the work we build for you, while third-party libraries and services keep their own licenses.
Established, well-supported frameworks chosen for maintainability and your hosting environment, typically modern PHP or JavaScript stacks with relational databases. We explain the choice in the scope.
You receive documentation and a handover walkthrough. Ongoing support for fixes, updates and improvements is optional and agreed separately.
Often, yes. We start with a review of the code, its tests and its dependencies, then recommend whether to extend, refactor or replace parts of it.
Next step
Describe the users, the workflow and the tools involved. We will help you decide whether custom software is the right investment and what a first version should include.
We reply by email. An inquiry is not a contract, and there is no obligation.