Insights · Custom applications
When a website stops being the right shape.
Some problems are not pages. When a business needs something that works with its own information, runs a real workflow, or holds data for its users, it needs software. These articles cover where that line sits and what building across it actually involves.
Articles
They support our custom application work, which is designed around the workflow first and reviewed by a person throughout.
All insights →- When You Need an Application, Not a Website How to tell when a business problem has outgrown pages and needs software, the signs that appear first, and what building an application actually involves.
- How VetCaseIQ Was Built How a veterinary case-review platform was built: structured documents, a multi-stage pipeline, literature retrieval, and where human review stays essential.
How to read this cluster
Where a page stops being enough.
The line between a website and an application is easier to see than it sounds. A website presents information the business already decided on. An application does something with information a user gives it — it holds state, applies rules, and produces a result that did not exist before the user arrived. Once a business needs the second thing, adding more pages will not get it there.
Most requests for new software turn out to be workflow problems. Something is being retyped between two systems, or a decision is being made by whoever happens to be free, or the same twenty questions are being answered by email every week. Those are worth solving, and the interesting part is usually the workflow rather than the technology.
Whatever tools are involved, they work as components inside a system that has been designed, tested, and reviewed, with a person responsible for what it produces. No system described here runs without that review.
Where this fits
What these articles connect to in the custom applications work itself.
Questions
What people ask before reading further.
How do I know whether I need an application rather than a website?
Ask what the thing has to remember and what it has to decide. If the answer is nothing — it presents information and collects an enquiry — a website is the right shape. If it has to hold a user’s data, apply rules to it, and give back a result, that is software, and building it as pages will not work.
Want this applied to your site?
One conversation, a review of the current site, and a clear proposal. No pressure and no long-term contracts.