01 / Initial setup
Design & development
An initial project cost covers the agreed analysis, functional design, development and launch preparation.
The amount reflects the scope, complexity and integrations your system needs.
Systems, shaped around your work
We listen to how your team works, then design a connected system around your processes, people and decisions.
Let’s talk about your work See how it takes shapeA familiar starting point
A request in a message. A plan in a spreadsheet. A detail only one person remembers. As the business grows, keeping everything together becomes a job of its own.
We start by understanding those connections — and where a clearer system would make a difference.
Our approach
Your system begins with your business, rather than a catalogue of modules to buy. Together, we define what it needs to do, how information should flow and who needs access.
We can reuse proven technical foundations while shaping the workflows, screens and connections around your reality. Start with the priority. Add what is useful as the business evolves.
How we work
A shared understanding first.
A working system, step by step.
We talk with your team, observe the work and understand what needs to become easier.
Together, we define the flow, rules and responsibilities before development begins.
A first working version makes the ideas tangible. Your team tests it and helps refine it.
We prepare the agreed data and access, and support the team as the system enters daily use.
Real use reveals the next priorities. We agree on improvements as your needs change.
Your team stays part of the conversation at every stage.
Where we can help
A system in practice
For Sunfield, the starting point was day-to-day coordination: jobs, people, planning and time records. The resulting Job Planner brings those connections into one place.
One example of a tailored system. Your starting point may be entirely different.
A clear cost structure
The scope comes first.
The proposal follows.
01 / Initial setup
An initial project cost covers the agreed analysis, functional design, development and launch preparation.
The amount reflects the scope, complexity and integrations your system needs.
02 / Monthly fee
A monthly fee reflects the size of the system, the services included and the choice of shared or dedicated infrastructure.
Maintenance and support are defined in your proposal. New features and integrations are scoped separately.
Two ways to host
Shared infrastructure uses a common technical environment with company data and access kept separate. Dedicated infrastructure gives your system its own database environment. We assess the appropriate option together.
No. We design your system around the needs of your business. The starting point is the work you need to organise, rather than a menu of modules to subscribe to. Proven technical components help us build, but the workflows and connections are defined with you.
We begin by understanding what already works well. Together, we identify what to preserve and where a change could reduce repeated work, confusion or missing information. The aim is a system your team can use in practice.
No. We can begin with a priority process and a clearly defined first version. Other areas can follow as the team gains experience and the next needs become clear.
We assess integrations during the design stage, including the capabilities and access offered by each service. Where a connection is feasible and useful, it can be included in the agreed scope.
We define access around people and responsibilities. Different team members can have different views and permissions, so each person can work with the information and actions appropriate to their role.
Company data and access are separated even when the underlying infrastructure is shared. A dedicated database environment can also be agreed where your needs call for it.
The monthly fee covers the hosting and ongoing services specified in your proposal. Its level depends on your system, infrastructure and agreed maintenance and support. Additional development is assessed separately, so the scope stays clear.
Yes. We can review how the system is being used and agree on changes, new workflows or integrations. Each improvement is assessed for its value, scope and cost before development.
Start with a conversation
You don’t need a technical brief. A process that takes too long, a recurring problem or an idea is a good place to start.
Let’s talk ricardoneves13@gmail.com