How we work

Clear ownership. Practical delivery. A defined next step.

Every engagement starts with a useful piece of work to own. We agree the boundaries, get the work done with your team and make the next decision on what the work actually shows.

01

Agree what needs to move.

Start with the business objective, what is already known and who commissions the work. Agree the specific responsibilities Aught will own and the decisions that remain with your team.

02

Give the work clear boundaries.

Define scope, budget, dependencies, client inputs and evidence or acceptance criteria. An existing platform and an approved requirement are valid starting points. Agree capacity and the people needed before work begins.

03

Execute with the right people involved.

Commercial and technical tasks can sit in one project, with each contribution clear. Keep an agreed backlog, a reporting rhythm and a visible record of decisions, progress and issues that need attention.

04

Review the actual assignment.

Validation is judged on evidence. Business development is judged on meaningful commercial progress. Implementation is judged on agreed functionality and operational readiness. Ongoing capability is judged on delivery, quality, continuity and its remit.

05

Decide what happens next.

Hand over, agree a new scope or continue with a defined operating arrangement. None is automatic. Documentation, working assets, dependencies and transition support should make the next step deliberate.

AI-native in practice

Better tools.
The judgment stays human.

We use AI in research, prototyping, development and operations to move work forward and incorporate feedback. We review outputs, test software and distinguish evidence from assumptions.

Your project does not need to be an AI product. Real customers, actual workflows and the agreed acceptance criteria determine whether the work is useful. We agree what information can be used and how tools fit the assignment; confidential client material is not a shared resource across engagements.

Roles, trust and the work itself

Clear on whose behalf.
Clear on what belongs to whom.

When a provider introduces us, or we work with more than one party, the proposed scope makes the roles explicit: who commissions the work, who is represented, what each party receives and who makes the buying decision. Relevant commercial interests are disclosed before they affect a recommendation.

A vendor’s licensed core, authorized shared-platform development and customer-specific configuration or integrations carry different rights. Handover, source access, third-party licenses, hosting and maintenance are agreed for the actual engagement.

We reuse general methods and explicitly reusable components. Identifiable research, lead lists, pipeline data, confidential requirements and proprietary code are not passed between clients without appropriate permission.

Useful questions

Before we
get started.

Do we need an AI product?

No. AI-native describes how Aught works across research, prototyping, development and operations. Your project can be an ordinary software, commercial or operating problem. Human judgment and real-world evidence remain central.

Can we start with implementation?

Yes. We start with the actual need and the decisions already made. An approved requirement or a chosen platform can be enough to define an implementation; a separate validation engagement is not a prerequisite.

What to scope after choosing a platform
Can we engage you for only positioning, product work or business development?

Yes. We can agree a focused scope in any of those areas. You can engage us for one part of the work or a defined project from start to finish.

Can you work with our team or provide ongoing capacity?

Yes, through an agreed remit. We define responsibilities, capacity, specialist participation, backlog, reporting and a transition plan. A lighter fractional arrangement may suit the work.

Do we have to use a particular software platform?

No compulsory vendor purchase is part of this offer. The approach depends on your requirements, existing technology and the engagement. A referral is not required to work with Aught.

How do you handle provider relationships?

We agree who we represent and what we are responsible for. Any relevant commercial relationship is made clear before it affects a recommendation or introduction. We clarify who commissions each piece of work, what each party receives and who makes the buying decision. Distinct work is scoped and charged transparently.

Can customer information be passed to other clients?

Not without appropriate permission. Only agreed inputs are shared for the defined work. Identifiable research, lead lists, pipeline information, confidential requirements and proprietary code are not inputs to someone else’s engagement. Reuse is limited to general methods or explicitly reusable components.

What happens when an experiment does not work?

We review the evidence and its limitations, then decide whether to change direction, stop or gather more information. A test that supports a clear decision can be useful even when the original idea does not progress.

What do we receive at handover?

The assets, evidence, documentation and transition support agreed in scope. We distinguish the vendor’s licensed core, authorized shared-platform changes and customer-specific work. Source access, licenses, hosting and ongoing support depend on the engagement and third-party rights.

Guides and insights

Let’s make it work

What do you want to make happen?

A clearer offer. A new customer or market. A working implementation. Ongoing product and delivery support for the next stage. Tell us where you are and what needs to move forward.

Discuss a project