Led by a founder with more than 21 years of experience

contact@guilda.io

Digital Transformation

Software development services

We build internal business applications, web applications and portals for your customers, integrations and APIs, and mobile apps, or take over code another team started. The code and the repositories are yours from the first day.

Overview

Software Development is part of GUILDA's Digital Transformation practice. We build the software a company needs when nothing on the shelf fits, connect it to the systems it already runs, and leave the company owning all of it.

What we build

Most of what we build falls into four kinds. Internal business applications replace the spreadsheets, email chains and workarounds a team has outgrown with dashboards, workflow tools and back-office systems that follow how the work is really done. Customer web applications and portals give your customers a place to sign in, order, follow what they ordered and get service without calling. Integrations and APIs connect the systems you already pay for, so the same data is not typed into three of them, and let partners or your own applications reach your data under control. An integration is often the smallest useful project of all: it removes a manual step your team repeats every day without replacing any system. Mobile apps put the same tools in the hands of staff in the field or of your customers, on iOS and Android.

We also take over software that another team started. Sometimes the original developers moved on; sometimes the project stalled. We review the code first and tell you what state it is in, then carry it on.

Languages and platforms

We write TypeScript, React, Next.js and Node.js for web applications and APIs; Python; Java; C# and .NET; and Go. Mobile apps are built with Flutter or React Native, so one codebase serves both iOS and Android. Where the software runs in the cloud, it is deployed together with our Cloud Transformation work when you need both.

Before the code

Larger systems are worth designing before they are built. Our Architecture Design service produces the solution architecture, the architecture review and the technical specifications, documented with the C4 model, and it can come before a build or stand on its own. For smaller projects, the design step inside the project covers the screens, the data and the integrations, and the written scope says which of the two your project needs.

How it is priced

Every project starts with a written scope that names the deliverables and the duration, and says whether the work is fixed price or time and materials. A fixed price suits a project whose scope is settled before it starts, such as an integration between two known systems. Time and materials suits one that will take shape as it goes, such as a new product whose users are still being discovered. Most projects take two to four months, and larger systems six months or more. Support after launch is a separate monthly retainer, agreed only if you want it.

What you keep

The code and the repositories belong to you from the first day, not transferred at the end. Every project ends with documentation of how the software is built, deployed and run, and with a hand-over to your team. Support after launch is available as a monthly retainer, but the software never depends on it: your own developers, or anyone you choose, can take it from there.

Who it suits

Mid-sized companies, roughly 50 to 1,000 employees, with a small IT team or none, that need software built and someone accountable for it. Companies whose own IT team needs extra hands or a skill it lacks for one project. And startups and product teams building something new. We work with companies in the United States and Mexico, and every project is led by our founder, Marco Villarruel. If you are not yet sure whether to build software or buy a product, a current-state assessment from Digital Transformation Advisory or our IT strategy work answers that first, in two to six weeks at a fixed price.

Security in the build

Software is easier to secure while it is being written than after it ships. GUILDA's Cybersecurity practice sets secure coding standards and secures build pipelines, containers and Kubernetes clusters under its Engineering Security service, and a software project can include that work, scoped alongside the build. Our founder holds the CASE, a certification in application security engineering.

Software that handles customer data or payments should be tested before it goes live. Red Teaming & Penetration Testing tests web applications, APIs and mobile apps the way an attacker would, and it is scoped separately from the development work.

Deliverables

What you get

  • Internal business applications

    The tools your own staff use every day, such as dashboards, workflow applications and back-office systems, built around how your team actually works instead of how a packaged product assumes it does.

  • Customer web applications and portals

    Web applications your customers sign in to, to place and follow orders, see their accounts, download documents or ask for service, on a phone as well as a desk.

  • APIs and integrations

    Connections between the systems you already run, so that data entered once reaches everywhere it is needed, and APIs that let partners or your own applications reach your data safely.

  • Mobile apps

    Apps for iOS and Android, for your staff in the field or for your customers, built with Flutter or React Native so that one codebase serves both platforms.

  • Taking over an existing codebase

    When another team started the software and can no longer continue, we review what exists, tell you plainly what state it is in, and carry it on from there instead of starting again by default.

  • Documentation and hand-over

    Every project ends with documentation of how the software is built, deployed and run, and a hand-over to your team, so they can operate and change it without depending on us.

  • Maintenance and support

    After launch, if you want it, we keep the software up to date and fix what breaks, as a monthly retainer you can end or change as your own team grows.

Process

How an engagement runs

  1. Scope and price

    We start from what the software must do, who will use it and what it must connect to. You receive a written scope that names the deliverables, the duration and whether the work is fixed price or time and materials, before anything is built.

  2. Design the solution

    We agree the screens, the data, the integrations and the technology before writing the bulk of the code, so that the cost of a change is low while it is still on paper. Larger systems can start with our Architecture Design service.

  3. Build

    2 to 4 months, up to 6 or more

    We build the software in your repositories from the first day, so the work is visible to you as it happens. Most projects take two to four months; larger systems can take six months or more.

  4. Launch and hand over

    We put the software into use with your team, then hand over the code, the documentation and the knowledge needed to run it. From then on your team operates it.

  5. Support, if you want it

    Maintenance and support after launch continue as a monthly retainer. It is optional, and the software and everything needed to run it stay yours whether you take it or not.

Proof

Credentials and partners

Marco Villarruel, Founder & CEO

  • CASE

FAQ

Frequently asked questions

Who owns the code you write for us?

You do, from the start. The code lives in repositories that belong to you, not copied over at the end of the project, so you can see the work as it happens and nothing depends on us handing it back. The documentation we write for the hand-over is yours too.

How long does a project take and how is it priced?

Most projects take two to four months, and larger systems six months or more. A project can be fixed price or time and materials, depending on how settled its scope is. Which one applies is agreed in the written scope before anything is built. Maintenance and support after launch, if you want them, are a monthly retainer.

Can you take over software another team started?

Yes. We start by reviewing the code, how it is built and deployed, and what is documented, and we tell you plainly what we find, including when part of it is better rewritten than repaired. Then we carry it on.

Do you support the software after launch?

Yes, if you want us to. Maintenance and support continue as a monthly retainer, covering updates and fixes. It is never a condition of the project. Every project ends with documentation and a hand-over, so your own team, or anyone you choose, can run the software instead.

Related

Cloud Transformation

Cloud migration services to AWS, Microsoft Azure or Google Cloud: a landing zone, infrastructure as code, the migration itself and cloud cost optimization.

Red Teaming & Penetration Testing

Penetration testing services for web apps, APIs, networks, cloud and Active Directory, plus red teaming. Every test ends with a report and a retest.

The engagement

Duration
2 to 4 months, up to 6 months or more
Pricing
Quoted for each engagement

Fixed price or time and materials, agreed in the scope before work starts. Maintenance and support after launch are a monthly retainer.

Next step

Tell us what you want built

What it should do, who will use it and any deadline. We reply within two business days.