Do we need designs before we contact you?
To get started, tell me who will use the application and what they need to do.
We’ll work through the screens and workflows together. Existing designs, sketches or examples are a helpful starting point.
Can the application be used on smartphones and tablets?
Yes. I design for the devices your customers and staff actually use.
I consider the task as well as the device. A customer submitting a request on a phone may need a different view from a staff member reviewing cases at a desk.
I build and test those workflows at the screen sizes and in the browsers your users rely on.
Can we continue to use our existing data and systems?
I check what information is already available and how the application can access it.
I identify what to migrate, what to retrieve through integrations and what the new application needs to maintain itself.
What does it cost to develop a web application?
Cost depends on how many workflows and screens you need, who can use them, and which systems they connect to.
Existing data, document processing and deployment requirements also affect the work.
With the first release defined, I can quote for it or work within an agreed budget for the first phase.
Can we offer the web application as our own software product?
Yes. I can build the features you’ll need to offer the application to your own customers.
These might include separate customer accounts, team management, subscriptions, and billing.
More about SaaS and MVP development →