This is where your app, platform, or system gets built. We work in two-week cycles called sprints: before each one we agree on exactly what will be built, at the end you see it working in a demo, and you decide whether to continue. Each sprint has a fixed price. At Alset we call them Product Sprints.
It is a common worry when you pay for software: weeks go by and there is nothing to see. Working in sprints fixes that. Every two weeks you see working software in a demo, compare it with what was agreed, and decide whether to continue. You pay sprint by sprint, not for months of work you cannot see.
Product Sprints are for products that already have:
written requirements,
a list of what will be built (the backlog) and a technical design (the architecture),
and enough validation to build.
They are not for open-ended scope or for “we will figure it out as we go”. If you do not have that list yet, our software development estimate produces it →
(the backlog). Each sprint has a closed list of what will be built.
with clear goals and a defined scope.
in a demo at the end of the sprint.
with the next sprint.
We set up the servers, automate how new versions are published, run final testing, and release, with a 30-day bug warranty after launch.
See the launch phase →With a scope agreed before each sprint, a fixed price per sprint, and new requests placed in later sprints instead of added on the fly. You decide, sprint by sprint, whether to continue.
First the requirements are written, then the work is estimated, and then it is built in short cycles: each one adds working functionality until the first version is complete. Then it is launched.
The work is split into short, fixed cycles called sprints, two weeks each in our case. Each one has a closed list of what will be built and ends with a demo of working software.
Working functionality added to your product, a demo, and visible progress against the list of what will be built.
USD 4,000 per two-week sprint, fixed price.
It depends on your product. The estimate phase tells you, with a timeline, before you commit to the build.
Yes. Each sprint runs from a closed, approved list of work.
A new request is evaluated, prioritized, and placed in a later sprint, so the sprint in progress is not disrupted. If a feature is removed, that sprint is not charged.
Sprint by sprint. Each sprint is paid in advance, and you approve the progress before the next one starts.
Sprints run from an approved list of what will be built. If you already have that list and a technical design, we review them first. If you do not, the estimate phase produces them.
Not for building a product: sprints give you more control over what gets built and how progress is measured. If you already have product direction and need more engineers, that is staff augmentation, which is billed by the hour.
See staff augmentation →The next step is the launch: taking the product to production.
Two-week sprints at USD 4,000 each, with a closed scope and a demo at the end of every one.