Skip to content
Valentina Vanegas Aristizábal

Work / At work

Team and product · At work · Since July 2026

A team and its products

Three developers across six products, from the first conversation with a customer to the production release.

Status
Reporting to the CEO
Role
Head of AI & Technology
Period
Since July 2026
Note
Described by type of client and by result. No client names, code or internal figures.

Abstract

I joined a startup in July 2026 as the person who decides what ships. In my first ten weeks I moved the company off a no-code app builder before its deadline, rebuilt the HR platform as a real codebase and moved the team’s planning into GitHub.

I lead by writing things down: goals with a clear “done when”, rules that AI coding agents follow, and a release process anyone on the team can read. That’s how a team of three keeps six products moving.

Team

  • Lead a team of three developers across six products for architecture and engineering, P&C insurance, HR and PEO, construction and B2B data.
  • Delegate through written goals with a clear "done when", instead of day-by-day plans.
  • Mentor an apprentice developer from SENA, Colombia's national vocational training service, in working with AI coding agents through written goals and the reasons behind them.
3developers
6products
Fig. 1 Architecture and engineering, P&C insurance, HR and PEO, construction and B2B data.

Delivery

  • Decide what goes to production, through release pull requests into a protected production branch.
  • Set the team's delivery workflow: contribution guide, PR template, mandatory CI, small pull requests with spec-driven tasks, and a gated workflow for production database migrations.
  • Wrote the rules for AI coding agents across the team: agents may open pull requests but never merge, and production data changes are run by a person.
  • Moved engineering planning from ClickUp to GitHub, with automations that move cards as the code moves and require a ticket for every pull request.
Delivery flow: a small, spec-driven pull request (agents may open one but never merge); mandatory CI; a release pull request, where I decide what goes to production; the protected production branch, with database migrations through a gated workflow. Small pull request a spec-driven task;agents may open, never merge Mandatory CI PR template · contribution guide Release pull request I decide what goes to production Protected production branch migrations through a gated workflow
Fig. 2 How a change reaches production. Small pull requests pass mandatory CI; a release pull request into the protected production branch is where I decide what ships.

Product

  • Led product for CRM, payments and client portals, and took the company's four apps from first build to launch on the App Store and Google Play.
  • Rebuilt the HR platform's prototype as a maintainable codebase and took it to production ten days later.
  • Led the company's move off a no-code AI app builder before its account-deletion deadline, moving code and databases to company-owned infrastructure.

From customer to code

  • Led discovery with a specialty subcontractor and reframed the request from "an AI that prices jobs" to "bid on more projects without hiring another estimator", then built a clickable prototype that treats quantity takeoff as assisted, never autonomous.
  • Built demo environments with fictitious data and bilingual product sheets for five products, so a demo never touches a real customer's data.

Where to find it

Public store pages, checked on 21 November 2026.