Skip to content

Custom AI Systems & Integrations

For a defined operating need that off-the-shelf tools do not meet: internal search, a business-specific tool, an integration between systems. We write the specification, build around what is already in place, and leave the business owning it.

Talk to us about a custom system
Custom AI system build specification by Black Applied: sample cover and acceptance criteria page on a desk
At a glance
Format

Specified build around an existing operating requirement.

Duration

Agreed in the written scope.

Output

A working system that meets its acceptance criteria, its specification, and ownership of the code, data and accounts.

Pricing

Priced on the written specification, fixed before any work starts.

Pricing.

Specified buildPriced on the written specification

What moves it: the integrations, the data quality and the acceptance criteria. Every build gets a written specification, with the fixed price in it, before any work starts.

100% of an Assess fee credits toward this service if it starts within 60 days of the audit.

Who it is for

Businesses with a need that no product quite meets.

The tools on the market do most of the job. The part they do not do is the part that matters. This is what that usually looks like.

  1. 01

    Two systems that should talk still need a person between them.

    Orders in one, stock in another, invoices in a third. Someone spends part of every day moving information across by hand.

  2. 02

    Staff cannot find what the business already knows.

    The answer is in an old email, a shared drive, or someone’s head. People ask the same questions and get different answers.

  3. 03

    An off-the-shelf tool does most of the job.

    The remaining part is the business’s actual process, and the tool cannot be bent to it.

  4. 04

    A spreadsheet has become a system.

    It runs a real process, several people depend on it, and it breaks when someone sorts a column.

  5. 05

    An earlier build left with the contractor.

    Nobody has the source, the credentials, or an understanding of how it works. It cannot be changed, so it is worked around.

Custom AI system build specification cover, Black Applied sample
What we do

We build what the operating requirement needs, and nothing else.

Custom software is expensive to own. We only recommend it where a defined requirement cannot be met another way, and then we build the smallest thing that meets it.

  1. 01

    Write the build specification.

    Problem, current state, proposed system, integrations, acceptance criteria. What “done” means, in writing, before anything is built. Where an existing tool would do, the specification says so and the build stops there.

  2. 02

    Build around the systems already in place.

    Integrations with what the business runs on today rather than replacements for it. Data stays where it lives. The new system reads and writes to it under the business’s own credentials.

  3. 03

    Keep the business as owner.

    Code in a repository the business controls. Accounts, keys and data in the business’s name. Nothing that depends on us to keep running.

  4. 04

    Hand over with documentation and a support path.

    A plain-language guide, a technical one, the acceptance test record, and a clear statement of how changes are made and who can make them.

What we do not do

Custom software should be the exception, and owned when it is built.

These are the lines we hold so that a build stays a good decision after it is live.

We do not build a product to sell to other businesses.

We do not replace a working system to use newer technology.

We do not start without written acceptance criteria.

We do not keep ownership of anything we build.

What you receive

A working system, and everything needed to own it.

The system is the point, but the specification, the tests and the ownership are what make it an asset rather than a dependency.

Build specification acceptance criteria page, Black Applied sample
01

The working system.

Meeting its acceptance criteria, in operation, connected to the systems it was specified to work with.

02

The build specification.

Problem, current state, proposed system, integrations, acceptance criteria. Kept current through the build.

03

The acceptance test record.

Each criterion, how it was tested, and the result. Signed off by the business.

04

Ownership: source, accounts, data, documentation.

Everything in the business’s name, with a written statement of how changes are made and who can make them.

How it runs

Five steps, in order. Duration agreed in the scope.

The specification comes first and is signed before the build starts. Nothing is accepted that was not in it.

01

Scope

The operating requirement, the systems involved, and whether a build is justified at all.

We look at the requirement with the people who live with it, and say plainly if an existing tool or a workflow would meet it. Custom software is expensive to own, so it is the exception.

02

Specify

Problem, current state, proposed system, integrations, acceptance criteria. Signed by the business.

The specification is written first and priced from, so what “done” means is fixed before anything is built. If the requirement changes during the build, the specification and the criteria change in writing with it.

03

Build

Around the systems in place, in accounts the business owns, with progress visible as it happens.

We build around what the business runs on today, and the data stays where it lives. Code sits in a repository the business controls, with accounts and keys in the business’s name.

04

Accept

Each criterion tested and recorded. Signed off by the business, not by us.

We work through the acceptance criteria with the business one at a time, recording how each was tested and what the result was. A criterion that is not met stays open until it is.

05

Hand over

Documentation, source, credentials and a support path, all in the business’s name.

The documentation is two guides, one plain-language and one technical, alongside the acceptance test record. It also states how changes are made and who can make them, whether that is the business’s own team, another developer or us.

Questions

Things people ask before they commission a build.

If yours is not here, ask. Answers here are short on purpose.

How do you decide whether we need custom software?

The scope step answers that. If an existing tool or a workflow will meet the requirement, the specification says so and the build stops there.

Who owns the code?

The business. Source in a repository the business controls, accounts and data in the business’s name. We do not keep ownership of anything we build.

What happens if we want to change it later?

The documentation and the support path say how. The business can make changes itself, use another developer, or ask us. None of those depends on the others.

Will it work with our existing systems?

That is the point of it. The specification names the integrations, and the acceptance criteria test them.

What if the requirement changes during the build?

The specification changes with it, in writing, and the acceptance criteria are updated. Nothing is built to an unwritten requirement.

Do you build products?

No. We build systems for one business’s defined requirement, owned by that business.

Contact

Have a need that no tool quite meets?

Tell us what it is. If a build is not justified, we will say so, and say what would do the job instead.