Custom software & SaaS
We develop customer portals, internal tools and first versions of SaaS products. Roles, records and daily workflows define the first useful release.
An internal tool the team uses every day. A login for your customers. The first version of something you want to sell. The useful question is who uses it, and what they need to finish.
We start from how the work happens now, usually in a spreadsheet or an inbox, and build the smallest version that replaces that. Not every idea at once. At handover I go through how you run it, so it does not depend on me sitting next to you.
Before We start
Three things are enough. Who uses it. What they have to finish. How that same job happens today.
The fee is for that first version. If understanding the problem needs paid time, I ask first.
IN PRACTICE
The first release should complete a specific job.
A customer portal might need file uploads, status updates and messages. We define what each user needs to complete, then develop screens and data structures around that work.
Get the starting point clear.
An existing spreadsheet or an example of the current process is useful. Anonymous examples are enough; there is no need to share real personal records.
Can features be added later?
Yes. We discuss the first release and likely future needs at the start. Additional features are scoped and priced separately, with maintenance responsibilities agreed at handover.
Describe the work as it happens this week, not the full product you imagine in a year.
Describe the work