Skip to content

Custom Software

Software built around how your business works.

Fidalgo develops systems and integrations when operations need a workflow that current tools cannot provide. We also evolve existing applications, considering data, maintenance and business continuity.

Discuss a software project

Who it is for

For companies relying on spreadsheets, facing rework between systems or turning a business process into a digital product.

Problems we address

  • Spreadsheets and manual tasks have become critical to operations, with limited visibility and control.
  • ERP, CRM and other tools do not exchange the information needed for work to move forward.
  • An existing system has accumulated limitations and needs to evolve without an immediate full replacement.

Possible deliverables

Internal systems and portals

Applications for teams, clients or partners, with workflows, access rules and information based on the real process. A first release can focus on the most valuable step.

Integrations and automation

Connections between APIs, ERP, CRM and external services. Failure handling, traceability and synchronization rules are part of the design.

Application modernization

Assessment of the current system, improvements to critical areas and staged evolution. Work can include architecture, data, tests and preparation for maintenance.

How to start

Bring the process you need to change, current tools and people involved. We organize the problem, dependencies and priorities before defining the first delivery. An MVP validates a hypothesis; essential requirements still need to be addressed.

From context to operations

  1. Understand the workflow

    Map users, business rules, data and integrations, identifying what already works and what needs to change.

  2. Define the first delivery

    Prioritize scope, state exclusions and establish acceptance criteria and responsibilities.

  3. Build and validate

    Implement in stages, test integrations and validate workflows with users. Scope adjustments are discussed throughout the engagement.

  4. Prepare operations

    Organize deployment, documentation and knowledge transfer. Agree how maintenance and new requests will be handled.

Questions about working together

Can you work on my existing system?

Yes. We first assess code, architecture, data and dependencies. We then propose staged improvements or replacement when there is a technical and business reason for it.

How do we avoid an undefined project scope?

Priorities, deliverables, acceptance criteria and exclusions are stated in the proposal. New requests are evaluated for their effect on timing, cost and dependencies before being included.

Are source code delivery and maintenance included?

Deliverables, code access, documentation, support and maintenance are agreed in the proposal and contract. Post-delivery operations need defined owners and terms.

Specific services within this pillar

  • APIs and Integrations

    APIs, webhooks and synchronization between ERP, CRM and existing systems. Integrations with data rules, permissions, failure handling and traceability.

Next step

Describe the process, who uses the system and which change matters most right now. That helps define a workable first delivery.

Discuss a software project