Team(Seven)

Seven people build all of it.

Every part of Core 137 — the takeoff canvas, the cost maths, the workspace around them and the invoice at the end — is designed, written and shipped by the people on this page.

That covers the whole width of the product: drawings and measurement, the cost database behind an estimate, scheduling, the file archive, billing and the account itself. One team carries all of it end to end, which is why the seams between those surfaces are the part we care most about.

It also covers the parts nobody advertises — the migrations, the audit trail, the release checks, the support thread at seven in the morning when a bid is due. There is no separate group here for the unglamorous half of the work.

Founder

Jose Baloa created the platform.

Founder and Chief Executive Officer. He built the first version of Core 137 and still owns its direction — what gets made, in what order, and how it has to behave on a jobsite before it is allowed to ship. He reads the support queue.

Portrait — Jose Baloa

The rest of the table.

Six executives, one for each discipline the company actually needs. Every one of them builds; none of them exists to manage the others.

Portrait
LuffyCofounder · Chief Operating Officer
Portrait
Taylor SylvaChief Administrative Officer
Portrait
Denisse BaloaChief Financial Officer
Portrait
Adrian UrbinaChief Creative Officer
Portrait
Sophia UrdanetaChief Experience Officer
Portrait
Paola UrbinaChief People Officer
Accountability

Who owns what.

One name against every part of the company. If something here is wrong, slow or unclear, this table tells you whose desk it lands on.

01Product & platform direction
JBJose BaloaFounder & CEO — what ships, and in what order
02Delivery & operations
LLuffyCofounder & COO — release cadence, support, uptime
03Business administration
TSTaylor SylvaCAO — contracts, vendors, company records
04Finance & billing
DBDenisse BaloaCFO — pricing, invoicing, the books
05Brand & creative
AUAdrian UrbinaCCO — identity, this site, every surface you read
06Product experience
SUSophia UrdanetaCXO — research, interaction design, the takeoff canvas
07People & hiring
PUPaola UrbinaCPO — who joins, and how they are supported

No shared ownership, no committees, no rotating on-call. Where a discipline needs two people, it is split into two disciplines.

How we work.

Three commitments a seven-person company can actually keep. The table above is what makes them checkable rather than aspirational.

  1. 01.You reach the builderA support thread lands with the person who wrote the surface you are asking about. There is no tier one, because there is no tier two to escalate to.
  2. 02.Every surface has one ownerWhoever builds a surface owns its data model, its tests, its migrations and the support it generates. Nothing is somebody else’s problem by design.
  3. 03.A decision takes a conversationChanging direction is an afternoon, not a quarter. We treat that as the one real advantage of staying small, and we spend it deliberately.

Talk to the people who build it.

Talk to us