When spreadsheets, emails and separate programs make collaboration difficult, a dedicated application can bring order to data, tasks and responsibilities. We start with the problem your team needs to solve.
Tell me what your software needs to do
When you really need custom software
Bespoke software makes sense when the way your company works calls for features that available tools do not adequately support. Before designing a new application, I work with you to check whether configuring an existing product more effectively or connecting the systems you already use would be enough.
A bespoke solution may help you manage a case from entry to closure, collect data from several departments or provide clients and colleagues with a private area. The initial question is practical: which task needs to become easier, more manageable or more accessible?
- Internal tools: dashboards for tracking enquiries, tasks, progress and documents.
- Business web applications: browser-based interfaces with different features and permissions for each role.
- Customer portals: viewing information and submitting requests through a dedicated workflow.
- Integrations with existing systems: exchanging the necessary data between the application, the website and compatible services.
These are types of work to consider, rather than a package of features already included. Explore my portfolio of web projects and applications to see the kind of work I develop.
An initial release focused on one complete workflow
A long list of features makes it difficult to decide what matters. I prefer to start with a workflow that people can use from beginning to end: for example, someone submits a request, a manager assigns it, the team updates it, and the person who submitted it can see its status.
For each step, we define who can take action, which data is required and what happens if an error occurs. The result is a scope against which to assess a proposal, verify the software and gather feedback from the people who will use it.
If the main need is to transfer data between programs, business process automation may address it with a more focused solution. If you need to present services and receive enquiries, a professional website may be the starting point.
From problem to delivery
- Analysis: users, activities, tools in use, available data and technical constraints. Requirements are translated into features with observable behaviour.
- Design: information structure and screens for the main steps, to review before developing the parts that would be most expensive to change.
- Development: implementation in verifiable stages, planned integrations and access management.
- Checks: testing the agreed user journeys, permissions, error handling and use on the intended devices.
- Delivery: deployment to the agreed environment, operating instructions and agreement on access, documentation and next steps.
The collaboration process includes review sessions: people who know the business need to be able to correct assumptions before they become final features.
Data, management and costs to clarify from the outset
An application also encompasses what happens after the first login. Before starting, we define where it will be hosted, what data it will process, who will manage users and permissions, how backup and recovery will be handled, and which external dependencies it will need.
The quote depends on workflow complexity, the number and quality of integrations, data migration, supported devices and management requirements. Hosting, subscriptions, maintenance and new features should be distinguished from initial development. We also agree on the handover of code and documentation as part of the scope.
The trade-off with bespoke software is that you can adapt the product to your process, but it needs ongoing maintenance. If an existing service meets the need, comparing it before investing in development is part of the analysis.
Working with the people who will use the software
Development starts with discussions with a main contact and the people who will use the application. We can work remotely and review how it works together against the agreed priorities. To learn about my background, visit the about Mattia Sica page.
Questions about bespoke software development
Can I start with an Excel file?
Yes, it can be a useful starting point for understanding the data and rules. I check formulas, duplicates, data volumes and who works on the file. Not every spreadsheet needs to become an application.
Will the software work with my business management system?
It depends on the interfaces and access available. Integration is assessed before the quote, based on the required features, documentation and any provider limitations.
Do I need to prepare a technical specification?
No. Examples of tasks, screenshots and templates with dummy data are useful. We can use this information to define users, requirements and criteria for checking the result.
Will I be able to add features after the first release?
The project may evolve over time. Initial priorities and subsequent changes are documented, so each new feature has a clear purpose and a clear impact on timelines, costs and maintenance.
Describe the work the software needs to simplify
Tell me who will use it, what you do today and which tools you already have. You do not need to choose a technology: we need to understand the result you want to achieve. Request a discussion about your business software.