TechNoteConsult

Four ways we work with you.

Once you’ve described the problem, one of these shapes fits. Each says what you get, how long it takes and who it is not for. The people on it are the experts we recommend and you choose.

Four stepping stones: find, ship, build, keep

Find where it works

A readiness sprint.

2–4 weeks

We sit with your team, map how work really flows and pick the one place where automation will pay for itself first. You leave with a plan you can act on, with or without us.

Who it is for

Leadership teams who know something should change but have not settled where to start.

What you get

  • Map of three to five candidate workflows, ranked
  • One recommended first use case with an expected payback
  • Data and access check: what exists, what is missing
  • Compliance checklist for your sector and data
  • A staged rollout plan with owners

Not for you if: You have already chosen the use case and need delivery, not discovery.

Ship it into your stack

Solution deployment.

4–10 weeks

We start from a solution that already works, adapt it to your data and rules, and connect it to the systems you run today. No rip-and-replace.

Who it is for

Teams with a clear use case and systems they want to keep.

What you get

  • Working solution connected to your systems
  • Human review and appeal route where decisions affect people
  • Training for the people who will use it
  • Run-book and handover documentation
  • Success measures agreed at the start and reported at the end

Not for you if: You need something that does not exist in any form yet. See co-build.

Build something new

Co-build and custom engineering.

8–16 weeks

Where we have the pattern but not the whole product, we build the rest with you, and you keep a say in every decision. Web, mobile and back-end engineering under one roof.

Who it is for

Organisations with a specific workflow, or a product idea, that off-the-shelf tools do not fit.

What you get

  • Scoped build plan with milestones you can approve
  • Working increments every two weeks
  • Production-grade code and documentation you own
  • Security and data-protection review before launch

Not for you if: You want a fixed price on a vague idea. We scope first, then commit.

Keep it working

Managed operations.

Ongoing, monthly

Solutions drift. Data changes, rules change, people leave. We monitor, tune and support what we shipped so it keeps earning its keep.

Who it is for

Teams that want it running without hiring a specialist to babysit it.

What you get

  • Monitoring and a monthly health report
  • Fixes and tuning as your data and rules change
  • Named engineer and an agreed response time
  • Quarterly review of what to automate next

Not for you if: You plan to run it all in-house from day one. We will hand over cleanly instead.

Three shapes. Quoted after we talk.

We do not publish a price list, because scope decides price. We do publish what each engagement contains and how long it runs, so you know what you are buying.

Readiness Sprint

Know where to start.

2–4 weeks

  • Workflow mapping
  • Ranked use cases
  • Data and compliance check
  • Rollout plan

Ideal for: Leadership teams choosing a first move.

Deployment

Get one thing live.

4–16 weeks

  • Solution adapted to your data
  • Integration with your systems
  • Training and handover
  • Human review built in

Ideal for: Teams with a clear use case.

Managed Operations

Keep it earning.

Monthly

  • Monitoring and tuning
  • Support with response times
  • Quarterly review
  • Roadmap for what comes next

Ideal for: Teams that want it to run itself, with someone accountable.

Five stages, from first call to handover.

  1. Week 1

    Listen and map

    We shadow the work. Who touches a case, in what order, with which tools. We find the rework and the waiting.

  2. Weeks 1–2

    Pick one thing

    We choose the single use case with the clearest payback and the cleanest data. One thing, written down, with a measure.

  3. Weeks 2–4

    Prove it on real work

    We run it on your own cases, side by side with how you do it now, and show you the results, including where it gets things wrong.

  4. Weeks 4–8

    Ship it alongside

    It goes live next to the old way first. People review its output. We turn it up as trust builds.

  5. Week 8 on

    Hand over, or keep running it

    Your team takes the controls, or we stay on to run it. Either way you own the documentation and the data.

Before you ask.

We have no technical team. Can we still do this?

Yes. Most of the people we work with do not. We bring the engineering, connect to the systems you have, and train your people to use and supervise it. If you want a technical owner on your side later, we help you define the role.

Will this replace our staff?

It replaces tasks, such as retyping, chasing and sorting. In every workflow we ship, a person reviews the unusual cases and makes the decisions that affect customers. Most teams use the hours they get back to do work that was always waiting.

Our data is a mess. Is that a dealbreaker?

Rarely. The readiness sprint includes a data check so you know what is usable today and what to fix first. Some of the best first projects, like reading documents, work well on messy inputs.

How long before we see something working?

A readiness sprint gives you a plan in two to four weeks. A first working deployment typically lands between four and ten weeks, depending on how many systems it touches.

Is our data safe? What about the Data Protection Act?

We design for the Data Protection Act, 2012 (Act 843) from the start: registration as a data controller, handling of special personal data such as health records, breach duties, and the right to ask a person to reconsider an automated decision. We tell you what applies to you and build it in. We are not your lawyers, and we will say so when you need one.

What does it cost?

It depends on scope, so we quote after the first conversation. Finding the opportunity is agreed up front. If you then choose experts we place, we earn a commission, and we explain how before you choose. Each engagement has a defined duration and deliverables.

What if it does not work for us?

The readiness sprint exists to answer that cheaply. If the numbers do not justify a build, we say so, and you keep the plan. Later stages have agreed checkpoints, so you can stop when the evidence says to.

Do you work outside Ghana?

Yes. We are based in Accra and work remotely and on site across Africa and beyond. Our hours overlap with Europe and cover most of Africa in a normal working day.

Bring us the problem. We’ll bring the experts.

Describe what you need solved. We recommend the right people and you choose. No obligation.

Describe your problem See how it works