Core commitments
Everyone who works with us should be better off for having done so.
Sigao exists to solve real problems with technology and leave people better off for it. These eight commitments are how we hold ourselves to that, especially on the engagements where it’s inconvenient.
Nº 01 People Come First
Dignity, agency, trust.
The company, the software, and the process all exist to serve people. When something has to give, we protect dignity, agency, and trust first, because progress that costs people those things isn't progress.
Read the essay: What 'People Come First' looks like in practiceHow we live this
- We turn down engagements that would grind our team down.
- Engineers sit in client meetings, not just leads and account managers.
- Burnout gets tracked as a delivery risk, like any other.
- Knowledge transfer runs through the whole engagement, so the last week isn't a scramble.
What we reject
Treating people — clients, teammates, or end users — as interchangeable resources.
Nº 02 Relationships Drive Results
Trust is the foundation.
The best outcomes come out of the best relationships. We work with respect, honesty, and integrity because nothing else holds up under the weight of a hard problem.
Read the essay: Why relationships drive results in agentic deliveryHow we live this
- We deliver hard truths early, even when honesty costs us scope.
- Each Engagement Lead goes deep with one or two clients instead of spreading across ten.
- Problems surface mid-engagement, not in an end-of-engagement post-mortem.
- When we're not the right fit, we say so and point you elsewhere.
What we reject
Hiding bad news to protect a contract or quarter.
Nº 03 Accountability Stays Human
Never outsourced to AI.
AI and automation speed the work up. They don't take the responsibility for it. We invest in the people who steward our systems, because you can't outsource accountability to a model.
Read the essay: Accountability stays human, even when the agents helpHow we live this
- We own what ships. Engineered guardrails hold the quality bar on every change, so human judgment goes where it compounds — improving the harness itself.
- AI suggestions feed a decision; a person still makes it.
- Anything AI-influenced in production has a named human owner.
- When an AI incident happens, the postmortem interrogates our process, not the model.
What we reject
'The agent shipped it' as an answer for anything that matters.
Nº 04 Learning Is Paramount
Growth as a goal.
Growth isn't a side effect of the work; it's part of the point. An engagement should leave our people, our clients, and their users more capable than it found them.
Read the essay: Learning as a deliverableHow we live this
- We name the skills your team will walk away with before the work starts.
- Pairing is how we work by default, not a special occasion.
- Time to practice and research is paid time, not after-hours.
- Mistakes get written up, shared, and folded into how we onboard the next person.
What we reject
Knowledge hoarding that turns vendors into permanent fixtures.
Nº 05 Move Fast and Build Things
Quickly, never recklessly.
We move quickly, never recklessly, and never by burning out the team. Speed without responsibility breaks products and people. Speed with judgment is what compounds.
Read the essay: Move fast and build things without breaking peopleHow we live this
- We write the spec first. Clarity is the cheapest accelerator we own.
- We push back on a deadline invented for its own sake.
- Validation runs continuously, so the surprises don't all land on the last day of the sprint.
- Every stage has a quality gate. Nothing ships unreviewed.
What we reject
Performative urgency that masks a lack of clarity about the goal.
Nº 06 Ethics, Built-In
Confront harm honestly.
We build with ethics and integrity. In practice that means naming the trade-offs, facing harm and bias honestly instead of around it, and owning our share of the impact while we create real value.
Read the essay: Ethics, built in, not bolted onHow we live this
- Every AI use case gets a risk, IP, and bias review before it rolls out.
- We say the trade-offs out loud. There's no free-lunch framing here.
- An engineer can raise a harm concern without putting their career on the line.
- We walk away from work that would harm users, profitable or not.
What we reject
'It's just a tool' as cover for irresponsible deployment.
Nº 07 Outcomes Over Output
Value, not volume.
Success is the problem solved, not the feature count. We hold ourselves to the numbers a CFO will sign off on — cycle time, deployment frequency, defect-escape — and to the human outcomes those numbers stand in for.
Read the essay: Outcomes over output: a working definitionHow we live this
- We tie success metrics to what users and customers actually got, not to how many tickets closed.
- We report DORA-style measures — cycle time, deployment frequency, defect-escape — that hold up in a board review.
- What we ship is the measure, not what we put in.
- Quarterly reviews ask one blunt question: did this matter? Sometimes the answer is to sunset it.
- Demos put real users on real work, not a slide narrative.
What we reject
Velocity metrics that reward churn.
Nº 08 Transparency Builds Trust
Especially when it's hard.
We communicate plainly. We share what matters, tell the truth when it's hard to tell, and keep the commitments we make.
Read the essay: Transparency builds trust, including the hard partsHow we live this
- Bad news leads the weekly report. It doesn't get buried at the bottom.
- We walk you through pricing and engagement structure before anyone signs.
- We show our methods, including the approaches that didn't pan out.
- Estimates come with a confidence range. We won't fake precision we don't have.
What we reject
Performance theatre over honest communication.
Why this matters
Technology is only meaningful when it serves people first.
If a Sigao engagement leaves your team less capable, more anxious, or more confused than they started, we’ve failed, regardless of what shipped.