Product setup and connection
Use one current Phoenix Tree AI product, connect the available read path and configure it for the team's own records and review routine.
Custom builds
Adapt the system to one real workflow.
Custom work starts close to current product work already underway. The best project is narrow enough to test, connected to a source we can inspect and important enough that a person already checks it by hand.
Ways to work together
Begin with the nearest proven path.
Workflow adaptation
Extend a current product around one missing source, calculation, approval step or output that can be tested against real work.
New-field pilot
For a repeated workflow outside finance or commerce, first prove that the data, rules and acceptance checks fit the same evidence-led system.
Current bases: Global Markets Research and Open Commerce Workbench. Both remain in development, so a custom engagement does not turn either one into a supported public release.
A workable brief
Four conditions make a good fit.
- The work repeats and currently depends on manual checking or reconciliation
- The source data can be exported or reached through a documented connection
- A good result can be judged from examples, rules or a written acceptance check
- A person can remain responsible for approval and external action
Not a fit today
Work we will decline
- A general chatbot with no defined work behind it
- A broad digital transformation programme
- Autonomous payments, trading or marketplace writes
- A project that depends on data we cannot lawfully or reliably access
- A result that cannot be checked by a person who knows the work
Process
Scope the acceptance path before the build.
- 01
Fit check
Start with the repeated task, current operator, source system and one example of a good result.
- 02
Evidence map
List every source, deterministic rule, model judgement, review point and external permission.
- 03
Written scope
Agree what will be built, what will stay out and how the finished path will be accepted.
- 04
Build on real work
Test the narrow path against representative inputs, including missing and conflicting records.
- 05
Handover
Deliver the files, configuration, connection notes and operating instructions in the client's own environment.
Handover rule
Your data, accounts and working files remain yours.
Price and delivery time are quoted only after the evidence map and acceptance boundary are clear. There is no public package price while the offer is still being defined.
First email
Describe the smallest task that keeps coming back.
Three lines are enough: what repeats, where the source data sits and how a person decides that the result is correct.