How we work

A clear path from scope to release.

Five stages. Each one ends with something you review and a decision you make.

Our software development process

From first conversation to release

  1. 01

    Conversation

    You tell us what you want to build or change and why now. We come back with questions and a first view of the scope.

    You decideScope it together?

  2. 02

    Discovery and scope

    We agree exactly what the first release delivers and what it leaves out, with acceptance examples and a fixed price.

    You decideApprove scope and price

  3. 03

    Design and technical approach

    Designers and engineers plan the flows, the screens and the architecture together, before anything is built.

    You decideApprove the approach

  4. 04

    Build and verification

    The work moves in milestones. You try each one in a test environment before the next one starts.

    You decideAccept each milestone

  5. 05

    Release and handover

    We release, watch real usage and hand over everything needed to run and develop the product.

    You decideContinue or take over

What you get

Something real at every stage

  • Scope and a fixed price

    What the first release includes and leaves out, with acceptance examples and a fixed price you approve.

  • Flows and architecture

    User flows, key screens and the technical approach, agreed before the build starts.

  • Working software, by milestone

    Each increment runs in a test environment. You accept it against its examples.

  • A product you own

    You own the code and design files, with access from day one and documentation for future development.

  • Control where your data goes

    Your data is excluded from AI provider training, and hosting in your own infrastructure is supported.

  • 30 days of fixes after handover

    Bugs within the delivered scope are fixed at no extra cost for 30 days after handover.

Real timelines

Two to four months to release

Four client projects, month by month. Point at a month to see what was built.

  • Legal research platformLive in production
    1. Month 1 Archive and indexDocument ingestion, OCR, the permissions model and a first index over part of the archive.
    2. Month 2 Workspace and launchSearch, cited answers, comparison and drafting. The full archive indexed and the system in production.
    3. Month 3 SupportWatching real usage, fixing what lawyers reported and tuning results on their actual questions.
    1. Month 1 Channels and modelConnecting the social networks, preparing past conversations and fine-tuning the model.
    2. Month 2 Inbox, scripts and launchDrafts in the inbox, tone of voice settings, script stages and auto-reply rules. Live in production.
    3. Month 3 SupportMonitoring live replies, adjusting rules and fixing what the team reported.
    1. Month 1 Agents and memoryThe agent builder, the coordinator, hand-offs and the shared memory with its cleaning step.
    2. Month 2 Guardrails, models, billingThe guardrail layer, the model router with hosted and open-source models, and Stripe subscriptions with limits.
  • Research data platformLive in production
    1. Month 1 Sources and ingestionThe data lake, databases, registries, APIs and scrapers connected through Kafka and Airflow.
    2. Month 2 ProcessingSpark jobs for cleaning, deduplication, entity linking and pruning.
    3. Month 3 Store and toolsClickHouse, SQL access, dashboards and notebooks.
    4. Month 4 Search and launchSearch and plain-language questions. The platform in production.
    5. Month 5 SupportHelping analysts move their work over and tuning what they found slow.
BuildSupport after launch

Ways to work together

  • A scoped project

    An MVP, a new feature, an integration or a website, for a fixed price agreed upfront.

  • A single service

    One specific piece of design, development or marketing work, scoped on its own.

    All services
  • Ongoing improvement

    Support, releases and new features after launch, from the team that built the product.

Who you work with

From Cursopic

Senior designers and senior engineers, with senior specialists in data or AI when the work needs them.

From your side

A decision owner and someone who knows the workflow.

Questions about working with us

  • What you want to build or change, who it is for and what is getting in the way. A walkthrough or screenshots help. A detailed brief is not needed, and neither are passwords or production data at this point.

  • It depends on the scope. The four client projects above took two to four months of build to reach production or a delivered MVP. A focused first release, such as an MVP, is planned around what has to be in it.

  • From the scope: the users and workflows the first release covers, the integrations, the data and the rules the system must enforce. We agree a fixed price for that clear scope before development starts. See what belongs in your first release and custom software development for what drives cost.

  • A new role, workflow or integration may change the estimate. We describe the change and its effect on cost and timeline, and you approve it before the work starts, or defer it to a later release.

  • Through an agreed timeline, regular progress reviews and clear deliverables at each milestone. Every change is reviewed by a second senior engineer, and you try each milestone in a test environment and accept it against the acceptance examples you agreed to.

  • The released software, the code and design files in your accounts and documentation to support future development. You have had access from day one. Bugs within the delivered scope are fixed at no extra cost for 30 days after handover, and ongoing support can be arranged.

  • External services and data access are agreed upfront. Your data is excluded from AI provider training, and hosting within your own infrastructure is supported.

  • Yes. Tell us what you need and we will agree confidentiality before you share anything sensitive.

  • Yes. We review the relevant code, architecture and data first, agree a focused scope for the next part of the product and work alongside your team where you have one.

Let’s build your next advantage

Tell us what you want to launch, improve or automate. Let’s discuss the scope and the next step.

Get in touch

Prefer email?

sales@cursopic.com

Cursopic

Tell us about your project

What would you like to launch, improve or automate? A few lines are enough to start.

We use what you send only to reply to you about your request. Privacy policy (opens in a new tab)

Prefer email?

sales@cursopic.com