Custom software
We build portals, apps and systems for small and medium businesses. We create new solutions and modernize existing ones, with integrations and AI where the project needs them.
Start with the idea or problem. You do not need a technical solution already designed.
Software ready for its intended use, with tests, documentation and a maintenance plan.
When this service makes sense
- A portal where customers can track requests
- An app for teams working in the office or in the field
- A system that needs new features or modernization
What we deliver
- Requirements, solution design and acceptance criteria
- A usable version with tests and documentation
- Operations, maintenance and improvement plan
Compare approaches before defining the project
- Alternatives
- Compare configuring an existing product, integrating current systems and building custom software. Evaluate the user task, actual constraints and maintenance.
- Initial scope
- One priority journey, its authorized users and a completion criterion. Portals, applications and modernization start with a verifiable slice.
- What affects time and cost
- Workflows and access roles, integrations, data migration, offline use, security and operating requirements. Assess reuse and dependencies before the proposal.
- Delivery and continuity
- The proposal defines acceptance criteria, documentation, responsibilities and access to the commissioned deliverables. Support, hosting, third-party services and future development have explicit scope and terms; they are not assumed to be included.
How we develop the project
The work advances in short stages, with documented decisions and review before expanding scope.
- step 1Portals, apps and internal systems
- step 2Improve existing software and integrate tools
- step 3Tests, documentation and preparation for maintenance
When this is not the right path
If an existing tool meets the need, building from scratch may not be worthwhile. Scope can be a single feature, integration or complete solution.
Questions to define scope
Short answers to understand when this path deserves to become a project.
Does the software need to use AI everywhere?
No. An application can serve its users with clear interfaces, rules and data. AI is included only when its contribution can be evaluated.
Do you integrate with existing internal systems?
Yes. The project considers internal systems, ERPs, operational databases, spreadsheets, APIs and workflows already used by operations, with fallback when integration carries risk.
Do you hand over the code or stay its owner?
Ownership, repository access, licenses and handover are made explicit in the proposal and contract. The architecture prioritizes standards and documentation that avoid unnecessary dependency.