FAQ
Common questions.
Working with us.
How do you differ from a consultancy, a software vendor or an IT services provider?
A consultancy typically advises on what should change and leaves the development and implementation to others. A software vendor sells a pre-defined product which requires your organisation to adapt its way of working to the software. An IT services provider develops, integrates and supports systems to a given specification, but is seldom involved in organisational redesign or business strategy.
One must also note that software development skills on their own do not guarantee a successful AI deployment. Success requires strategy, organisational design and engineering to work together, grounded in practical commercial judgement.
We take responsibility for the whole undertaking, shaped by your requirements and inputs. We begin by understanding where your organisation creates value, then plan, design, build and implement the solutions as working capabilities. As these enter daily use, we train your people to direct them, and evaluate and improve them over time.
Experts from strategy and engineering sit within one team, so the judgement about what to build, and how it will be used in practice, is not separated from the work of building it.
Which organisations are a good fit?
We have built solutions ranging from systems automating legal research and drafting in a firm's house style to systems tracking vast product distribution networks.
Almost any organisation that relies on recurring knowledge work can benefit, whatever its sector. Most business processes, from client intake and document review to reporting and back-office administration, can now be automated in whole or in part. The largest gains usually lie in the work through which an organisation creates value for its customers, which is why we typically look there first.
Fit depends less on size or technical maturity than on two conditions. Leadership should be willing to reconsider how the work is organised, rather than only adding tools to it. The people who know the work must also be available to help shape the system's design, as they will be the ones using it.
What happens after we reach out?
We arrange a first conversation, which carries no charge and no obligation or commitment. In exploratory conversations, it is useful when someone responsible for your organisation’s direction takes part, together with someone who knows the relevant work in detail.
You need not prepare anything before an exploratory conversation. It always helps, though, to have a sense of where your organisation creates most of its value, and one or two examples of work that consumes a disproportionate share of time or expertise.
Your people and information.
Who needs to be involved, and how much of their time will it take?
Typically, two groups need to be involved. The first is a senior sponsor with the authority to change how work is organised, who takes the decision at the end of each stage. The second is the people who know the work in detail, whose judgement defines what good output looks like.
During Discovery, we ask for interviews and the opportunity to observe the work as it is done. The demand on your experts is usually greatest during Build, when they help test the system against real cases and review its outputs. We agree the time required with you before each stage begins, and plan it around their other commitments.
What if our knowledge is scattered or our systems are dated?
Most organisations are in this position, and it need not prevent a start. Much of what an organisation knows sits in documents, email, precedents and the experience of its people, and seldom in a form a system can use directly. Our Discovery process establishes what is available, how reliable it is and who is permitted to see it.
The condition of your systems of record help determine the best starting place. Scattered knowledge may point towards a narrower first workflow, or towards organising the underlying information before a broader capability is attempted.
Where you want to keep your existing systems of record, we integrate our solutions with them. How closely we can connect to a system depends on whether it allows other software to read and update its data. Where an older system does not, we can work from regular extracts of its data instead. Where moving to a different system would bring a clear benefit, we can also assist with the migration.
Will this replace our people?
It is important to be clear that a successful AI implementation necessarily means that certain roles will change. Our aim is to multiply what your organisation can produce, rather than only to reduce what it spends. How the resulting capacity is used, including any decision about staffing, naturally remains yours.
We design with your people’s development in mind. In professional work, juniors have traditionally learnt their craft by doing the very work a system can now perform. Where that is so, the design should preserve a path by which they still acquire expertise and judgement, for example by reviewing the system’s work and handling the cases it escalates.
Helping you make the most of your existing people is part of what we offer. We work with you to identify new ways in which they can add value, for example by handling the most demanding matters, deepening client relationships or taking on work the organisation previously lacked the capacity to pursue. In many organisations, routine administration consumes much of the working day. Automating it frees your people to spend their time on work that creates value.
Technology and safeguards.
Why not simply give our staff a general-purpose AI assistant?
General-purpose assistants and tools can be very useful, and they often belong alongside a tailored capability. On their own, however, they tend to speed up individual tasks while the workflows, hand-offs and controls around those tasks stay as they were. The knowledge your people put into them can also end up scattered across personal conversations, rather than kept as an asset of your organisation.
A tailored capability is built around your knowledge, standards and verification, and changes the workflow itself. Sometimes, it is necessary to build a solution from scratch. Other times, the best path lies in combining existing models and tools with integrations and purpose-built components, in a mix that follows from what the work requires, what it will cost to run and how much control you need.
Which AI models do you use?
Unless you ask otherwise, we do not tie your organisation to a single model provider. Models are chosen for each task according to the quality the work requires, the sensitivity of the information involved and the cost of running them at your volumes. A single capability or workflow may well use more than one underlying model.
Models improve quickly, so we design systems in which a model can be replaced without rebuilding the work around it. Where information cannot leave your environment, models can run on infrastructure you control, although the most capable models are not always available on that basis. We are very sensitive to the security and privacy implications of all design decisions and will make sure that you understand exactly how the systems work and that they comply with your privacy requirements.
How do you verify the system’s work?
Verification is designed into every solution from the start. Like any person, an AI system can make mistakes, and its work must be checked in proportion to what is at stake.
Before a system is relied upon, it is evaluated against defined standards using real cases. In daily use, a verification layer checks its outputs, uncertain cases are escalated, and human review is concentrated on the aspects of the work where an error would matter most.
Current models can already perform highly complex work to a high standard, from financial modelling to legal drafting. They are also effective adversarial reviewers, adept at finding errors in work produced by people and by other systems. This allows first-pass review to be automated, so that your people spend their time on the cases that need their judgement and on overall quality assurance.
Your organisation remains responsible for the work it relies on, as it is for work done by its staff.
How is our confidential information protected?
Confidentiality and permissions are designed into the system from the start. Information keeps its source and access restrictions as the system uses it, so that no one obtains through the system what they could not see before.
The architecture settles where information is processed and stored, who can access it and on what terms any model provider handles it. We use model providers only on business terms under which your data is not used to train their models. Where the information requires it, processing can be confined to your own environment or a chosen jurisdiction, with consequences for the choice of models.
Where your systems will process personal information, we help you meet the requirements of the Protection of Personal Information Act, No. 4 of 2013 (POPIA). We design our systems with POPIA compliance in mind. Assistance also includes putting the necessary documentation in place, such as any relevant operator agreements, updated privacy notices and the arrangements the POPIA requires for transferring personal information outside South Africa (if applicable).
Cost, value and ownership.
What determines the cost and timeline?
Each stage is scoped and priced before it begins, so you know the cost of the next step before you commit to it. The main drivers are the breadth of the workflows involved, the state of the underlying information, the number and difficulty of integrations, the complexity and ambiguity involved, and the level of verification the work demands. The same factors generally determine the timeline.
A capability also carries running costs once it is in use, such as model usage, hosting, third-party services and support. We estimate these during Design, on the basis that a capability is worth pursuing only if its value comfortably exceeds what it costs to run.
Discovery itself may be a single session or run over weeks depending on the complexity of the envisaged solutions.
We endeavour to work as quickly as possible.
How will we know the investment is worthwhile?
An investment of this kind is worthwhile when the capability measurably improves the work it supports, at a cost its value comfortably exceeds. Knowing whether that is so typically requires measuring the work before and after the capability is introduced, against measures that matter to your organisation, rather than relying on impressions. We can help you put such evaluations in place, although the results depend on the work and on how the capability is used.
Time saved does not of itself appear in the accounts. It becomes value only when the capacity it frees is put to use, whether as greater output, better service, new work or lower cost. Part of our work is helping you decide which of these to pursue, and reshaping the surrounding work accordingly.
Value need not come only from doing existing work more efficiently. We can also help you add entirely new capabilities, or bring functions you currently outsource in-house, and equip your people to perform them well.
Who owns what you build, and can we run it without you?
Your knowledge and data remain yours throughout. Our design principle is that your organisation should be able to operate, change and move its capability without depending on us. A capability typically combines your information, work commissioned from us and third-party technology, and the engagement terms set out the ownership and licensing position for each.
After launch, you choose how much to rely on us. You may ask us to operate and develop the system, build an internal team to do so, or combine the two. In each case, the system is documented so that you can take over its operation whenever you choose.
Training and keynotes.
What training do you provide after implementation?
Training forms part of every implementation. We make sure the capability has been fully absorbed into daily work and that your people know exactly how to operate, supervise and improve it.
Do you offer training sessions?
Yes. We run training tailored either for teams or business leaders on the practical use of AI in their work. Courses can be customised to your organisation and to the tools your people actually use, so that what they learn applies directly to their daily work.
Do you give keynotes and talks on AI?
Yes. You may specify a topic, and we also speak on the subjects of our own research. Talks include technical explainers from our Engineering Lab, practical lessons from our Deployment Corps and discussions of the social and political questions AI raises from our Futures Bureau.
We also publish our research and thinking on an ongoing basis in the Thinking section of this site.
Another question?
Ask us directly. Exploratory conversations carry no charge and no obligation.
Reach Out