SageDynamics Discuss a project
Menu

From the first discussion to handover

We plan the first phase to end with a working system tested on your own examples. Your reviewers judge the results, and you decide what happens next before anyone relies on it more widely.

  1. Understand the task

    We discuss who does the work, what information they use and where they get stuck.

  2. Agree what to test

    We agree what the system needs to do, which examples to test and who will check the results. We also decide what should stay manual.

  3. Build and review

    We build against the agreed examples. Reviewers inspect source references, missing information and mistakes, then tell us what needs correction.

  4. Decide the next step

    Before wider use, we discuss who will run the system and what access, documentation and support they need. We also discuss monitoring, future changes and how to stop the system if necessary.

Before building

We discuss who knows the process, which examples we have permission to use, and any access restrictions or policies we need to follow. We also agree when your team can review the results.

Scope
We define the task, the output to prepare and what should stay manual.
Review
Your team checks the results before wider use.

Project questions

Do we need a partnership?
No. You can hire us for a standalone project for your team. Data-product and venture partnerships are a separate option.
Where do you work from?
Makati in Metro Manila. Our working day overlaps with Australia's, and with US teams we work mostly in writing, with calls at the start or end of your day.
What should we bring to the first conversation?
A description of one task your team repeats: who does it, what they work from and where it gets stuck. Leave out confidential documents. If a project goes ahead, we agree how to share real examples safely.
How long will it take?
That depends on the workflow, the examples and the access involved. After the first conversation we propose a first phase with its own timeline, ending in a working system your reviewers can test.
How is it priced?
We quote each engagement once we understand the scope. Fees, ownership, licenses and support are agreed in writing before work starts.
Who owns the result?
The agreement sets out ownership before work starts, covering your data and materials, the system we build, and any third-party tools or reusable components. Tell us early about any ownership requirements.
Will the system act without our approval?
Anything that needs approval waits for a person. Together we decide which outputs a person must check before they are used.
What if AI is the wrong tool?
Then we will tell you. Some problems are better solved with ordinary software or a change to the process.

Tell us what your team needs

Describe the task and what you want to change. We agree fees, ownership, licenses and support as part of the engagement.

Discuss a project