Skip to main content
Impart GlobalBegin the conversation
About

A practice with a long memory.

Impart Global builds A.I. systems for businesses that want their repetitive work carried. The practice runs on business experience that reaches back to 1998, and on a decade of building the digital systems that hold under load.

01 // The record

What the practice is built on.

i.Business Experience Since 1998Two decades and more of operating, building and shipping inside real businesses.
ii.10+ Years in Digital Systems & AutomationProduction systems, integrations and automated workflows across commerce, software and operations.
iii.Millions Generated Through Online VenturesOnline businesses built and run by the founder have generated millions in cumulative revenue.
iv.Member of the Hashgraph AssociationA member of the Hashgraph Association, the non-profit that supports the adoption of Hedera technology.

POPIA-compliant by default

Case studies are published once a client has signed them off, and not before. Until then the work is documented here in full: how it is scoped, how it runs, and what it is built on.

02 // The story

From digital systems to A.I., the discipline travels.

Impart began with operating real companies, building digital systems that ship, and running online ventures that earn. That practical record still decides how every engagement is scoped, priced and delivered.

Ten years and more of that experience sits in the same territory the practice works in today: systems, automation, and the integrations that keep them standing. A.I. is the newest shape the work takes. The operating discipline behind it is older.

Every system is scoped against a specific line on the client's ledger, priced so the savings fund the build, and given thirty days to earn its keep.

Our ambition reaches past individual projects. We are working toward a connected family of A.I. products, tools and platforms that put more capability in the hands of the people who create, build and run things, with the creative industries close to our heart. Today that means client systems and a handful of live apps; the rest is direction, and we label it as such.

The win sits in the operating model.
03 // The principal

One principal, on every engagement.

Impart runs flat. The person who scopes the work is the person who builds it, from the first call to the thirtieth-day review.

Liam Pitcher

Founder, Impart Global

Liam founded Impart and leads the build. He is the principal on every A.I. programme, from the data foundations to the agents that ship into production: POPIA-aware by default, vendor-agnostic at the model layer, and particular about operating discipline.

Focus
Build, integration, model selection
04 // What we hold ourselves to

Intelligence should extend human agency.

Useful A.I. needs clear ownership, human oversight and a design that respects the people it affects. These are the commitments we write into our work, and you can hold us to each one. They are operating and contractual commitments, without any claim of independent certification.

  1. 01Human controlPeople approve and override the decisions that warrant it, with clear escalation.
  2. 02Data boundariesWhat data a system may touch, and how sensitive information is treated, is agreed before it goes live.
  3. 03Clear responsibilityYou know what each system does and who answers for it.
  4. 04Real ownershipThe agreement separates what is built for you, which is yours, from the frameworks we bring and keep.
  5. 05Measured resultsWe set a baseline first, then test whether the system improves the work.
05 // How every engagement runs

Three phases, in order.

Wide at the beginning, precise at the end, like the spiral the work follows.

  1. Audit

    Days 0 to 10

    We map the operation, find the cost lines worth carrying, and scope a build that can earn its keep inside thirty days. The audit stands on its own: you keep the document whatever you decide.

    • Operating-model map
    • Cost-line shortlist with conservative estimates
    • Build scope, priced and timeboxed
    • Risk register and POPIA position
  2. Build

    Days 10 to 30

    Weekly cycles against the agreed scope. The data foundation comes first, the model layer second, the integration with your existing systems third. Production-grade from the first week.

    • Data foundation aligned to POPIA
    • Model selection note: vendor, residency, fallback
    • Integration into your operational systems
    • Production deployment, observability and runbooks
  3. Operate

    Day 30 and on

    The system is tuned against live data, with a written note each month on what moved. If the measure is unmet at thirty days, we keep working at no further cost until it is.

    • Tuning against live data
    • A monthly written note
    • Quarterly review against the original cost line
    • Continued work at no further cost until the measure is met
06 // What we build on

Chosen per engagement, kept swappable.

Five layers, selected for latency, residency, regulatory profile and total cost of ownership. The operating system around the model outlives the model, so the model layer stays replaceable.

  1. Models

    Vendor-agnostic at the model layer. Selection is a per-engagement decision driven by latency, residency, cost per token, and the regulatory profile of the use case.

    • Anthropic Claude
    • OpenAI GPT family
    • Google Gemini
    • Azure OpenAI
    • AWS Bedrock
    • Local open-weight models
  2. Data foundation

    Where most AI engagements actually fail. The data layer is architected first, with POPIA constraints baked in at the schema level rather than added on later.

    • PostgreSQL + pgvector
    • Snowflake / BigQuery
    • Pinecone / Weaviate
    • Supabase
    • S3-compatible object stores
  3. Orchestration

    How the agents move. Tool use, retries, fallbacks, queues. Boring infrastructure, kept that way deliberately.

    • LangGraph
    • Temporal
    • n8n / Zapier
    • Make.com
  4. Observability

    Every system Impart ships into production has telemetry from day one. You see the same dashboards we do.

    • Langfuse
    • Helicone / OpenTelemetry
    • Sentry
    • Custom KPI dashboards
  5. Front of house

    What the end user actually sees. Whether it is a chat surface, an embedded widget, or a back-office dashboard, the front layer is built for the operator who runs the function every day.

    • Next.js + React
    • Tailwind CSS
    • Vercel / Cloudflare
    • Custom dashboards
07 // Joining the practice

We hire deliberately.

There are no open roles today. When one opens, it goes to someone with years of shipping systems into production and keeping them alive afterwards; someone comfortable owning the cost a system replaces; someone who treats compliance as seriously as code, and writes plainly. If that reads like you, send a note with the most recent system you owned end to end.

Send a note

08 // Begin

Tell us what you're trying to change.

Start with the problem. We answer within one business day.

Rather talk? Ask us anything on WhatsApp. (opens in a new tab)

Within one business day.