Process

How we build products that businesses can run on

Sancilo takes products from discovery to production in a defined sequence: understand the problem, scope the first version, validate the architecture, build iteratively, and keep it running after launch. The goal is to reduce the risk of building the wrong thing — or the right thing badly.

Product Discovery

Before building, we define what should actually be built. Discovery is a distinct engagement for founders and teams who are not ready to commit to full development on day one.

  • Product requirements
  • User journeys
  • Feature prioritisation
  • MVP scope
  • Architecture direction
  • Technical roadmap
  • Development estimate

How we reduce product risk

  1. Define the MVP before development

    We agree what the first version must do — and what it deliberately will not — before a line of production code is written.

  2. Validate architecture before implementation

    The system design is reviewed against the real workflows and scale it has to support, so structural decisions are made on purpose, not discovered late.

  3. Build iteratively

    Work ships in increments against a prioritised scope, so direction can change while it is still cheap to change.

  4. Demonstrate working increments

    You see the product working at each step, not a status document describing it.

  5. Test before production

    Critical paths are tested before release, so the first users are not the test suite.

  6. Monitor after launch

    A shipped product is observed in production so issues surface from telemetry, not from a support ticket.

How projects are priced

Product development is scoped based on complexity rather than number of pages. These are the factors that determine scope and cost:

  • Product scope and the size of the first release
  • Number of platforms (web, mobile, backend)
  • User roles and permission complexity
  • Business workflows and their rules
  • Third-party and internal integrations
  • AI complexity, if any
  • Infrastructure and scale requirements
  • Security and compliance requirements
  • Testing depth
  • Timeline

Questions serious buyers ask

Will you understand my business?
Engagements start with discovery and requirements before development, so the build is shaped by your workflows rather than assumptions about them.
Will you disappear after launch?
Launch is a milestone, not the end. Ongoing product engineering, maintenance and iteration are part of how a product is run, not an afterthought.
Can you handle complex workflows?
Complex business logic — bookings, credits, payments, multi-role permissions — is where product engineering earns its name. The case studies show the architecture behind it.
How much will this cost?
Product development is scoped based on complexity rather than number of pages. The drivers above determine scope; discovery turns them into a real estimate.

Not sure where to start? Begin with discovery.

Start a product →