Skip to content

Available for projects

I build the software a real business runs on.

From the data model to the deploy. No middle layer, no handoffs, no team to coordinate.

At Home Software is a one-person studio. Six years as a full-stack developer inside US companies, and now two products of my own running in production for small businesses in Colombia.

years in full-stack development
6years in full-stack development
own products in production
2own products in production
person, from idea to deploy
1person, from idea to deploy

Work

Two products, built and shipped end to end.

Not demos. Both run in production, both are used by people who aren't technical, and I maintain both.

Own product · RetailIn production

Tendero

Inventory, sales and barcode scanning for a corner store. All from a phone.

A web app that replaces the shop's paper notebook: stock comes in, a sale goes out, and inventory reconciles at the end of the day without anyone counting shelves.

Next.js 16React 19TypeScriptPostgreSQLPrismaTailwind CSS+5
EscanearCámara activa

Arroz Diana 500 g

7702001120987

$3.200

18 en stock

Movimientos

  • Venta-2
  • Entrada+24
  • Venta-1
  • Ajuste-3
SUM(delta)= 18 ✓
Own product · Multi-tenant SaaSIn production

PideBot

A WhatsApp bot that takes the order and collects payment for the restaurant, 24/7.

Customers message the same WhatsApp number as always. The bot builds the order against the real menu, charges through Nequi, and drops it on the kitchen dashboard — with nobody sitting there watching the phone.

Node.jsTypeScriptFastifyPostgreSQLPrismaRedis+6
EFEl FogónWhatsApp

Buenas, me regalas 2 bandejas paisas 🙌

Listo. 2 × Bandeja paisa — $56.000. ¿Te lo confirmo?

Sí, confirma

menú → totalrecalculado en Postgres
orden #1042creada
Nequi / Wompipagado ✓

Services

What I can help with

Web applications are the focus. The rest I take on when it's the right fit for the client's problem.

Main focus

Web applications

The whole product: data model, back end, interface, authentication, roles, deployment, and whatever else it takes for real people to actually use it. It's what I do most and what I do best.

Next.jsPostgreSQLAuth & rolesDeployment

Websites

Fast, properly built sites for businesses and products: landing pages, catalogs, company sites. With editable content when that's what's needed.

PerformanceSEOContent

Mobile apps

For when a web app isn't enough. Also the middle path: a web app that installs to the home screen and uses the camera or works without signal — like Tendero's scanner.

PWACameraOffline

Contracting & team augmentation

Drop me into an existing team or codebase and I'm productive early. Six years of working inside code that nobody wrote yesterday.

HourlyPer projectRemote

Legacy rescue

The bug nobody can find, the job that falls over every week, the system only someone who already left understood. I read the code, work out what it's doing, and fix it.

DebuggingRefactoringDocumentation

Data & integrations

Moving data between systems without losing a row. ETL/ELT pipelines, app-to-app integrations, SSO, Power BI reporting, Elasticsearch-backed search.

MigrationsETL / ELTSSOPower BI

Capabilities

What I work with

Six years of corporate work leaves a long list. These are the tools I've actually delivered with.

Languages

TypeScriptJavaScriptC#.NETSQLHTMLCSS

Data

PostgreSQLSQL ServerETL / ELTElasticsearchRedisPower BIPrisma

Web

Next.jsReactNode.jsRESTServer ActionsTailwind CSS

Platform

DockerRailwayCI/CDSSO / OAuth / SAMLWebhooksBullMQ

Approach

One project, one person, no handoffs.

Working alone has one concrete advantage: nobody translates the requirement three times before it reaches the code.

  1. Understand the business first

    Before any code I want to see how it's done today — the notebook, the spreadsheet, the WhatsApp group. Good software replaces a process that already exists, and you have to know that process to replace it.

  2. Model the data before the screens

    Screens change; the data model doesn't. Get the model right and new features are cheap. Get it wrong and everything costs double, forever.

  3. Ship something working early

    A small piece in production beats a big plan in a document. You learn more from the first week of real use than from the third requirements meeting.

  4. Leave it maintainable

    Documentation, migrations, tests where they matter, and a deploy anyone can run. The project shouldn't depend on me being available.

About

Six years inside real systems.

Available for project work and remote contracting.

I spent six years as a full-stack developer at companies in the United States. That's where you learn what a greenfield project can't teach you: how to enter a codebase you didn't write, work out why it is the way it is, and change it without breaking what already works.

It's also where you learn the less glamorous, more useful half — migrating data between systems without losing a row, making two applications that know nothing about each other talk, standing up SSO, building reporting that business people actually use, and finding the bug that's been sitting there for months.

Now I work for myself. The two products on this page I designed, built and deployed myself, from the first database migration to the domain in production.

Contact

Tell me what you need built.

Send me the context: what the business does, which process hurts, and when you need it. I reply within 24 hours.

Or email me directly: johndiegoidrobo@gmail.com