# FAQ

> How Koombea prices work in story points, commits to a scope, and delivers it. Answers on engagement models, scope changes, and timezone overlap.

Source: https://www.koombea.com/faq/

---

How an engagement starts, how the price is set before work begins, and what happens when the scope moves. The questions specific to a capability are answered on that capability's page, and indexed below.


## Questions about working together

### How do we start working with Koombea?

Start with a conversation about what you are trying to ship. Next comes Scope Alignment, which breaks the work into a Work Breakdown Structure (WBS) and sizes every item in story points. You approve that scope and its price before any engineering begins.
### How do we get a price before we commit to anything?

That is what story points are for. We decompose your scope into a WBS, size every item, and price the total at a fixed rate per point. You see the number before work starts, not after. ScopeGen AI does the estimating, calibrated against what past projects actually took, which is what makes a committed price possible instead of a range.
### Can we test how you work before committing to a build?

Yes. The lowest-friction way is the free design audit. You send what you have already built, and you get back a written heuristic review and a prioritized list of usability issues in 2 to 3 business days, at no cost. It is a real deliverable rather than a sales call, which makes it a fair sample of how the work reads.
### What are the two ways to work with Koombea?

Two, and you pick one per engagement rather than mixing them. AI Pods is the default: a committed scope, priced in story points, delivered in two-week cycles. Staff Augmentation is hourly, for when you already have an engineering team and need capacity rather than a scoped outcome. Under that model you own the backlog and direct the work.
### What happens when the scope changes mid-build?

We size and price new scope exactly the way we sized the original, so you see what a change costs before you approve it. Reprioritizing inside the committed scope is a different thing and costs nothing. You re-cut priorities at every two-week boundary, so what matters most this cycle is your call.
### What happens if delivery slips?

The commitment is On Time & On Budget. Guaranteed. A fixed price against a committed scope means an overrun lands on us rather than on your invoice. That is also why Scope Alignment is thorough before it is quick. The estimate is the thing we are guaranteeing.
### Do you offer ongoing capacity instead of a fixed scope?

Yes, through a Monthly Capacity Commitment with Drawdown. You commit to a monthly volume of story points and draw against it as you scope new work. Unused points bank for 90 days on a rolling basis. They do not convert to cash, and they expire if the engagement ends, because an unbounded bank is an open-ended delivery liability.
### What hours does your team work?

Colombia hours, and our working day sits inside the US Eastern business day year-round. How We Work has the exact clock, including the one hour that moves seasonally because Colombia does not observe daylight saving.
### How will we see progress between releases?

The two-week cycle is a planning rhythm, not a release gate. Work reaches staging and production several times a week, so progress is something you use rather than something you read about. How We Work lists the reporting cadence that wraps around it.
### Where is Koombea, and how long have you been building software?

Koombea has built digital products since 2007, from Barranquilla, Colombia, with a US office in Naples, Florida. More than 200 of the products we have built are in market, and our development unit holds a CMMI-DEV/3 appraisal.
### What industries do you work in?

The deepest track record is in FinTech, payments and lending, and health services, where the binding constraint is usually regulatory rather than technical. We also build across Retail, ecommerce, and IoT. If your domain carries compliance weight, raise it in the first conversation rather than the last one.
### Do you work with startups, or only established companies?

Both. What changes is the engagement, not the standard of the work. A funded startup shipping its first product and an enterprise replatforming a system it cannot switch off both need a defined scope and a price they can plan against. What differs is how much discovery comes first before you can commit that scope.

## Answered in full elsewhere

- How We Work: Working hours and time zone overlap, your point of contact, the reporting cadence, and what happens when something breaks.
- Security and Compliance: What we attest to in writing, how we handle your code, data, and access, and where our responsibility ends and yours begins.

## Everything else, by page