We develop management software, customer portals and SaaS applications for businesses. Together we define the first essential workflow: who uses it, which data belongs together and what the application needs to accomplish.
We start with the people who will use it and the workflow they need to complete. This defines the features, user journeys and a clear scope.
Management software
Bring records, customers and required documents together in a web application. Your team can see the agreed status and related information.
A useful first scope: one workflow from creation to completion, with the necessary screens and access rights.
Customer portal
Give customers their own access to agreed documents, information or tasks. We plan what they can see and which changes they can make.
A useful first scope: sign-in, a defined customer area and one task your customers can complete themselves.
SaaS product
Offer your own software product. We define the first usable journey and agree on user roles, data and application operations.
A useful first scope: a core workflow you can review. Additional features and any required billing are explicitly planned.
Before the first line of code: a clear scope.
An application needs to remain operable and maintainable beyond its first version. That is why these questions belong in the planning phase.
Data and access rights
Which data is processed, who can see it and who can change it? These requirements belong in the agreed scope before development.
Existing systems
Which interfaces exist, which permissions are needed and what happens if an integration fails? Feasibility is checked before a commitment.
Operations and maintenance
Hosting, backups, updates and responsibilities need to be clear. Operations and further development are planned and quoted separately.
Handover and responsibility
Which credentials, documentation and usage rights do you need? What is checked at acceptance? These points are recorded in the proposal.
A first version you can review.
01
Understand the essential workflow
We look at who uses the software and what task it should solve. This defines a clear scope for the first version.
02
Agree on screens and features
A prototype shows how the application will work. Features, integrations and acceptance criteria are recorded before development.
03
Build in reviewable stages
Each agreed stage has a defined scope and budget. You review the implementation before we move on to the next features.
Agree on planning, implementation and operations separately.
We first agree on a requirements phase, then estimate implementation in defined stages with budgets and acceptance criteria. Operations and further development are planned separately.
Digital tools need a clear journey too.
Our own project combines topic-based guides, calculators and a digital enquiry flow. Content and tools can be used without requesting a consultation.
schweiz-start.ch complements the software example with a journey connecting information, interactive tools and an enquiry. It is our own project.
Which workflow takes up your time? Who will use the application? Which systems already exist? Start with the task rather than the technology.
When is custom software a suitable choice?
When an important business workflow cannot be adequately supported by existing off-the-shelf software. We first review your current workflow and possible adjustments or integrations. A custom application needs to offer a concrete benefit for the task compared with those options.
Do I need a finished specification?
No. A concrete workflow or product idea is enough for the first conversation. We then identify which features are actually needed.
Can the software connect to existing systems?
If suitable interfaces and access rights are available, we can plan an integration. We check feasibility before committing.
Can we start with a smaller version?
Yes. We define the essential workflow and separate later additions. This makes the first version straightforward to quote and review.
How is the software proposal prepared?
We first define the initial workflow, users, data and necessary integrations. Planning, implementation and acceptance criteria are agreed on that basis. Additional features, external licences and ongoing operations have their own scope.
Tell us about the workflow, people and systems involved. You do not need a finished specification for the first conversation.
What happens after your enquiry.
I reply personally by email. We then discuss what your project needs to do in a free, no-obligation first conversation. You receive a proposal with scope and price before commissioning any work.