Custom Software: your process, built into your own system

When no off-the-shelf software fits the way your company works, we build it for you and hand over the code.

  • Requirements gathering with your key users and UAT before go-live.
  • The code is yours: full intellectual property rights, repository, and documentation.
  • 30-day warranty and optional monthly maintenance.
Chat on WhatsApp

Tell us about your process, and we’ll let you know if this service is the right fit.

Is this service right for you?

This is for you if

This is for you if

  • You have your own processes that no off-the-shelf system covers and that are currently managed in Excel or on paper.
  • Your ERP handles accounting, but you have to handle the rest manually.
  • You know what you need to build—or at least what problem to solve—but you haven’t found anyone who will take it seriously.
  • You can engage your key users for the requirements gathering and UAT phases.
  • You want to own your system, not be a tenant of a generic tool.

This isn’t for you if

This isn’t for you if

  • You need AI or automation for existing processes, without building new software. That’s Operational AI + Automation.
  • You want a quick, inexpensive prototype without requirements gathering. Building without validation is high-risk, and we do not work that way.
  • You want a consumer app or a SaaS product to sell. That is product development—a different approach.
  • You cannot make your key users available. Without them, the system reflects our assumptions, not how your company works.

What’s your starting point?

Almost all companies start from one of these two points. The process adapts to yours.

  • Point A Build from scratch

    Point A Build from scratch

    There is no system that covers the entire process. Today, it relies on Excel, paper, or email, and it works as long as the person maintaining it is available.

    Signals

    • A critical process in a spreadsheet only one person maintains.
    • As volume increases, errors multiply.
    • Each area has its own version of the information.
    • Someone touches the wrong file, and the process breaks down.
  • Point B Expand what you already have

    Point B Expand what you already have

    You have an ERP that covers the basics. You handle the custom workflows it doesn’t cover separately, either manually or with standalone tools.

    Signals

    • The ERP handles accounting, not how you approve orders.
    • Reports that cross-reference multiple sources and are consolidated manually.
    • Screens or validations that the ERP vendor did not build.
    • Rules, permissions, or traceability that the base system lacks.

In both cases, the project starts with requirements gathering that turns your operations into a technical specification.

The systems we build

Three common formats, each addressing a typical scenario. The method is the same for all three.Note 2

Included in any projectNote 1

  • Functional requirements gathering with your key users: scope, acceptance criteria, and prioritized backlog.
  • Technical architecture based on size, criticality, and expected growth.
  • Development by modules, with internal review before each presentation.
See the other points
  • Internal QA and UAT with a list of acceptance criteria.
  • Full intellectual property rights: code, repository, and technical and user documentation.
  • Basic security: roles, activity logs, and backups.
  • 30-day warranty after go-live, within the delivered scope.

What This Service Is Not

  • Support Outside of Agreed Hours

    The SLA and hours of operation are defined at the outset. Extended coverage is quoted as a separate agreement.

  • Unlimited features

    Development is proceeding according to the approved scope. Changes to the scope are handled as additional phases.

  • Mass Migration of Historical Data

    It is not included by default. If your project requires it, it will be quoted and planned separately.

  • ERP Integration Without an API

    We connect through standard interfaces. Without an API, requirements gathering establishes what is possible, without promising what the infrastructure cannot support.

  • Company-wide Training

    We include targeted onboarding and documentation. Large-scale training is quoted separately.

  • Third-Party Licenses

    If the system requires licensed third-party tools, they are quoted separately or you can purchase them directly.

Project Phases

Each phase has deliverables and progress criteria. We do not move on to the next phase without validating the previous one.Note 3

  1. Functional requirements gathering

    Sessions with the sponsor and your key users. We map the current workflow and define rules, exceptions, permissions, and data. We sign an NDA beforehand.

    Deliverable Functional specifications, scope, acceptance criteria, prioritized backlog, and flowcharts.

    Deliverable

    Functional specifications, scope, acceptance criteria, prioritized backlog, and flowcharts.

  2. Technical Architecture

    We define the technology, databases, deployment, integrations, and security. You decide the business side: where your data resides, who has access, and how to scale.

    Deliverable Documented technical decisions and refined estimates by module.

    Deliverable

    Documented technical decisions and refined estimates by module.

  3. Iterative Development

    We build in modules, with internal review before each presentation. We don’t deliver everything at the end: we provide partial deliverables that you validate as we go.

    Deliverable Functional modules by iteration, change log, and test environment.

    Deliverable

    Functional modules by iteration, change log, and test environment.

  4. QA and UAT

    Internal QA verifies that the system meets the specifications. Next, UAT with your key users: real-world scenarios against the requirements gathered during the requirements gathering phase.

    Deliverable QA report and signed UAT acceptance record as a condition for go-live.

    Deliverable

    QA report and signed UAT acceptance record as a condition for go-live.

  5. Go-live and warranty

    Production deployment, targeted onboarding with your key users, and initial monitoring. The 30-day warranty covers bugs within the delivered scope.

    Deliverable System in production, technical and user documentation, and repository transfer.

    Deliverable

    System in production, technical and user documentation, and repository transfer.

  6. Monthly Maintenance

    Optional. Minor corrections, functional improvements, technical updates, and support for operational contingencies after go-live and the 30-day warranty period.

    Deliverable 10-hour monthly package, adjustable based on your needs.

    Deliverable

    10-hour monthly package, adjustable based on your needs.

  1. Functional requirements gathering

    Sessions with the sponsor and your key users. We map the current workflow and define rules, exceptions, permissions, and data. We sign an NDA beforehand.

    Deliverable Functional specifications, scope, acceptance criteria, prioritized backlog, and flowcharts.

  2. Technical Architecture

    We define the technology, databases, deployment, integrations, and security. You decide the business side: where your data resides, who has access, and how to scale.

    Deliverable Documented technical decisions and refined estimates by module.

  3. Iterative Development

    We build in modules, with internal review before each presentation. We don’t deliver everything at the end: we provide partial deliverables that you validate as we go.

    Deliverable Functional modules by iteration, change log, and test environment.

  4. QA and UAT

    Internal QA verifies that the system meets the specifications. Next, UAT with your key users: real-world scenarios against the requirements gathered during the requirements gathering phase.

    Deliverable QA report and signed UAT acceptance record as a condition for go-live.

  5. Go-live and warranty

    Production deployment, targeted onboarding with your key users, and initial monitoring. The 30-day warranty covers bugs within the delivered scope.

    Deliverable System in production, technical and user documentation, and repository transfer.

  6. Monthly Maintenance

    Optional. Minor corrections, functional improvements, technical updates, and support for operational contingencies after go-live and the 30-day warranty period.

    Deliverable 10-hour monthly package, adjustable based on your needs.

Typical Questions from a Requirements Gathering Session

Typical Questions from a Requirements Gathering Session

  • Who approves when the approver is on vacation?
  • What happens if the amount changes after approval?
  • Who can reverse a transaction, and what trace is left behind?
  • Which exception is handled by email today because the system does not cover it?
  • What is a person currently monitoring that should be controlled by a rule?

None of these are technical. They all define how the system is built.

Typical Questions from a Requirements Gathering Session

  • Who approves when the approver is on vacation?
  • What happens if the amount changes after approval?
  • Who can reverse a transaction, and what trace is left behind?
  • Which exception is handled by email today because the system does not cover it?
  • What is a person currently monitoring that should be controlled by a rule?

None of these are technical. They all define how the system is built.

What You Need on Your End

  • A sponsor with the authority to prioritize and determine the scope.
  • Your key users available for requirements gathering and UAT.
  • Access to current information: Excel files, forms, and process examples.
  • An initial definition of roles and permissions.
  • If there are integrations, your technical team will be responsible for granting access.

Without your input, the specification reflects assumptions, not your actual operations.

What You Need on Your End

  • A sponsor with the authority to prioritize and determine the scope.
  • Your key users available for requirements gathering and UAT.
  • Access to current information: Excel files, forms, and process examples.
  • An initial definition of roles and permissions.
  • If there are integrations, your technical team will be responsible for granting access.

Without your input, the specification reflects assumptions, not your actual operations.

What You Need on Your End

  • A sponsor with the authority to prioritize and determine the scope.
  • Your key users available for requirements gathering and UAT.
  • Access to current information: Excel files, forms, and process examples.
  • An initial definition of roles and permissions.
  • If there are integrations, your technical team will be responsible for granting access.

Without your input, the specification reflects assumptions, not your actual operations.

Who builds them and with what

Technology chosen for the project, not based on preference. If your IT team uses a different stack, we’ll evaluate it.

  • Functional Analyst:
    Functional Analyst:

    Translates your operations into rules, exceptions, and controls.

  • Full-stack:
    Full-stack:

    front-end and back-end integrated into a single role.

  • Backend:
    Backend:

    APIs, business logic, and integrations.

  • Frontend:
    Frontend:

    operational interfaces and usability.

  • DBA:
    DBA:

    data model and performance.

  • QA:
    QA:

    functional and regression testing.

  • DevOps:
    DevOps:

    deployment, CI/CD, and monitoring.

Reference Stack

  • Frontend

    ReactAngularAstro.

    Frontend

    ReactAngularAstro.

    React or Angular for operational screens, depending on the type of interaction; Astro for public sites and pages that need to load quickly.

  • Mobile Apps

    iOSAndroid.

    Mobile Apps

    iOSAndroid.

    For processes carried out in the field or via smartphone; if the project requires an app, this is determined during the requirements gathering phase.

  • Backend

    Java/Spring BootNode.js/NestJSPython (FastAPI/Django)Rust.

    Backend

    Java/Spring BootNode.js/NestJSPython (FastAPI/Django)Rust.

    Standard REST APIs; GraphQL if the data structure warrants it, and Rust for services where performance is critical.

  • Database and Infrastructure

    PostgreSQLMySQLAmazon AuroraSQL ServerDynamoDBSQLite.

    Database and Infrastructure

    PostgreSQLMySQLAmazon AuroraSQL ServerDynamoDBSQLite.

    Relational by default; DynamoDB when volume requires a managed NoSQL database, and SQLite for local data on a phone or in the field. Deploy on AWS, Azure, or your own infrastructure, with Docker, CI/CD, and basic monitoring included.

  • Authentication and Security

    JWTMicrosoft Entra IDAWS CognitoSSO/OAuth 2.0 or your own security system .

    Authentication and Security

    JWTMicrosoft Entra IDAWS CognitoSSO/OAuth 2.0 or your own security system .

    Role-based access control (RBAC) across all projects.

Project-Based Capabilities

Not every project needs the same capabilities. The project determines which ones are needed; they are not sold as extras.

  • Embedded AI

    Embedded AI

    Classification, extraction, generation, or prediction as another system module, with the same requirements gathering and UAT. A person reviews the result.

  • Operational machine learning

    Operational machine learning

    Analysis of historical system data to predict or detect anomalies, when the data supports it. Your team makes the decisions based on that.

  • IoT Connectivity

    IoT Connectivity

    Data captured from sensors and devices is integrated into workflows for operations involving physical assets or field logistics.

  • Integration with external systems

    Integration with external systems

    Via REST API or GraphQL when documentation is available. Without an API, we define a straightforward strategy during the requirements gathering phase.

Investment and Project Model

We publish the reference price. The exact cost depends on modules, workflows, and integrations.

Chat on WhatsApp

Tell us which process you want to turn into a system, and we’ll guide you on the scope and estimated cost.

What the CEO and IT Ask Before Getting Started

Is the code mine, and can I switch providers?

Yes. The code, repository with its history, and documentation are yours upon delivery. Any qualified team can take over without relying on us.

How do we verify that the system worked correctly?

With acceptance criteria defined before the first line of code is written. UAT is a formal validation using real-world scenarios. If it passes, it goes live; if not, it is corrected.

How is it different from a software factory?

The difference is how thoroughly the process is understood before writing code—the coding itself varies less between providers. What changes the outcome is understanding which exception breaks a rule and why a control exists after someone has experienced the consequences. We establish that during requirements gathering, with people who have operated and audited real processes.

What does the warranty cover, and what does it not cover?

It covers bug fixes within the delivered scope during the 30-day period following go-live. It does not cover new features, changes to requirements, or bugs caused by third-party modifications.

Does it integrate with my current ERP or system?

Yes, if your ERP or system has documented APIs. Integration is evaluated during the requirements gathering phase. Without an API, we define what is possible before committing to a scope.

In the cloud or on my own infrastructure?

It depends. The cloud is more agile and scalable, and we recommend it for most cases. Your own infrastructure makes sense with strict policies or an already established internal environment. This is determined during the architecture phase.

How much time do we need to devote to this?

Key milestones: requirements gathering sessions, module-by-module validations during development, and UAT at the end. If validations are delayed on your end, the schedule will be adjusted.

Can I add “Operational AI” later?

Yes, it’s the natural evolution. First, a stable system with clean data. On top of that, Operational AI adds automation, assistants, and analysis of the data the system generates—all reviewed by your team.

What if I change my mind during development?

Minor changes consistent with the agreed requirements are absorbed within the scope. Significant changes are evaluated as additional scope, with their impact on time and cost. Nothing changes without written agreement.

Which countries do you serve?

Headquartered in Ecuador. We work remotely with companies throughout Latin America, using standard collaboration tools.

How much longer are you going to keep using Excel for that process?

We start with a free orientation meeting: you’ll learn how we work, and we’ll let you know if this service is the right fit for you. If it makes sense to move forward, the requirements gathering phase defines what to build, what’s outside the scope, and the criteria for determining whether the system was built correctly.

Chat on WhatsApp

No blind quotes or budget commitments.

  • No upfront commitment
  • Free Orientation Meeting
  1. Deployment in the cloud or on your own infrastructure, depending on your company’s policies.
  2. A single project can combine formats; the method and what’s included remain the same.
  3. For reference: small projects, 4 to 6 weeks; medium projects, 6 to 10 weeks; complex projects, 10 to 16 weeks or more, in phases. This depends on your availability for validation.
  4. Reference price. The exact cost is finalized during requirements gathering.