# Akkord

> Most studios ship you a unit of work. We ship a motion that keeps improving.

Website people optimise for landings and traffic: how many arrived. We optimise the loop that starts after they arrive: getting the attention of someone who can actually buy, then removing every step between interested and paying. We watch where people drop off, change the surface, and measure whether the change worked. That runs continuously, not once at launch.

Method: More why questions than anyone asks for. Most briefs describe a solution someone already picked; the job is to get back to the intent underneath it. After that, every interaction and micro-action on the thing we build becomes data about whether we got it right.

Akkord builds intent-based websites, agent systems, applied AI development, and
integrations between services, all in service of that loop.

This site has no navigation. It exposes a single intent router that resolves a
plain-language brief into a position, a set of surfaces, a proposed run, and a
stack. The interface and this endpoint are the same router.

## Endpoint

POST /api/intent
Content-Type: application/json
Body: {"intent": "<1-600 characters of plain language>"}
Response: application/x-ndjson, one JSON object per line.

Event types:
- {"type":"resolved","kind":<intent kind>,"confidence":<0..1>}
- {"type":"delta","text":"<prose fragment>"}
- {"type":"surface","surface":{"id","label","note"}}
- {"type":"step","step":{"id","actor","action","detail","eta"}}
- {"type":"stack","stack":["..."]}
- {"type":"done"} | {"type":"error","message":"..."}

Rate limit: 20 requests per minute per client address.

## WebMCP

If you are an agent running inside a WebMCP-capable browser, do not scrape this
site. Load the homepage and call the tools it registers on
`document.modelContext`:

- akkord_resolve_intent: resolve a plain-language brief into a practice,
  confidence, position, surfaces, a proposed run and a stack.
- akkord_list_practices: the four service lines.
- akkord_list_clients: current engagements.
- akkord_get_engagement_model: how Akkord takes on work, and contact details.
- akkord_submit_intent_to_page: type a brief into the on-page console and
  resolve it, so the human watching sees the answer too.
- akkord_how_we_work: the loop from attention to paying, and what is measured
  at each stage.
- akkord_contact_channels: every live way to reach Akkord, with what each one
  suits and the usual response time.
- akkord_open_contact_channel: actually open email or WhatsApp for the person
  at the keyboard, with a message already drafted.

These tools read from the same source the interface renders, so a person and an
agent get the same answer.

## Intent kinds

- intent_web: Intent-based web
- agents: Agent systems
- integrations: Service integration
- ai_development: AI development
- engagement: Engagement
- company: About Akkord
- unknown: Open brief

## What Akkord does

- Intent-based web: interfaces that assemble around what a visitor wants, with a
  deterministic router underneath so the site works with the model switched off.
- Agent systems: durable execution, scoped tools over real services, an explicit
  permission boundary, and readable traces.
- AI development: retrieval, extraction, classification and routing, specified by
  an eval set and gated in CI on accuracy, cost and latency.
- Integrations: idempotent syncs, reconciliation, and one canonical contract that
  both humans and agents can call.

## Current clients

- Outercite (outercite.com): AI visibility intelligence: tracks brand citations
  across AI search engines and acts on them.
- getohdit (getohdit.co.za): AI-powered compliance, security, brand and
  discoverability audits for South African law firms.
- ALM Digital Media (almdigitalmedia.com): digital marketing for travel,
  accommodation and hospitality businesses across the UK, EU and South Africa.

## Engagement

Two-week diagnostic: the client's path from first attention to paying customer,
traced end to end with drop-off measured at each step. Then fortnightly build
increments, then the loop on a monthly footing. Full handover: the client owns
the repository, keys and data.

## Contact

- Email: agent@akkord.co.za (mailto:agent@akkord.co.za)
  Best for: A brief with any detail to it, or anything you want in writing. Usually same working day.

Preferred: agent@akkord.co.za. Lead with the actual problem rather than asking
whether Akkord does X. The first reply is more useful that way.