Customer portals and marketing workflow softwareLondon WC2Issue open for commissions
Commission

The portal issue

Portals your customers actually open.

IKAME designs and builds customer portals and the software behind marketing workflows: the approvals, briefs, asset requests and status updates that currently live in inboxes, spreadsheets and somebody's memory.

Illustrative still life: a dark phone leaning on a violet glass slab beside folds of yellow fabric
Illustration, AI-generated. Not our office.

Client portalsApproval flowsBrief intakeAsset requestsStatus pagesContent calendarsPartner hubs

Editor's letter

Software for the work around the work.

Most marketing teams do not lack ideas. They lack a reliable place where a customer, a partner or a colleague can send a request, see what happens to it and approve the result without a chain of forty emails. That gap is where we work.

IKAME LIMITED is a London software company. We build two kinds of things. The first is customer portals: logged-in spaces where your clients or partners submit, track, review and download. The second is internal workflow software for marketing operations: intake forms that become structured briefs, approval routes that know who signs off what, and calendars that are fed by real records rather than retyped every Monday.

We do not run advertising, buy media or promise campaign results. We have no ready-made platform to sell you a licence for. Each engagement is built around how your team and your customers already behave, then made a little stricter, a little clearer and much easier to follow.

This site is written like a magazine because we think software should be explained in sentences, not diagrams. Read the features, try the scope mixer, and if it sounds like your problem, commission us.

01

Feature one

The customer portal, considered properly

A portal is a promise: log in here and you will find the current truth. That promise breaks the moment a status is out of date or a file lives somewhere else. We design portals around the questions your customers ask most, and connect them to the systems where the answers are actually kept.

  • Request submission with structured fields instead of free text
  • Live status, owner and next step for every request
  • Proof and asset review with comments pinned to versions
  • Downloads that are always the approved version, never the draft
  • Role-based access for customers, partners and your own team
The full portal feature
Close crop of translucent violet glass catching light, illustrative
02

Feature two

Marketing workflows with fewer hand-offs lost

Inside the team, the same request touches strategy, copy, design, legal and the account owner. Each hand-off is a chance for the brief to drift. We build lightweight internal tools that hold the brief in one structured record, route it to the right reviewers in the right order and keep an audit of who changed what and when.

This might be a replacement for a shared spreadsheet, an approvals layer on top of your existing project tool, or a small application that feeds a content calendar from confirmed requests. We prefer integrating with what you already pay for to adding another login.

The workflow feature

If a customer has to email to ask where their request is, the portal has already failed.

A working principle, not a testimonial.

Who commissions this

Three situations we hear about

The agency with too many inboxes

You serve dozens of clients, each with their own way of sending requests. You want one front door with consistent intake, while each client sees only their own work.

The in-house team serving the business

Sales, product and regional teams all ask marketing for things. You want requests to arrive complete, prioritised and visible, so the team can say yes, no or later with evidence.

The brand working with partners

Resellers, franchisees or distributors need approved materials and a way to request local versions. You want control over brand use without becoming a bottleneck.

Interactive

Mix your scope before you call

Our portal scope mixer asks who uses the portal, what they need to do and what it must connect to. It writes a plain-English draft brief you can edit and send to us. Nothing is stored until you choose to submit it.

Open the scope mixer
  1. Audience. Customers, partners or internal teams
  2. Actions. Request, approve, download, track
  3. Connections. CRM, file storage, project tool
  4. Output. A brief written in sentences

The method, briefly

How a build runs

Listen

Short working sessions with the people who send and receive requests today. We read real examples, anonymised where needed, and map where things stall.

Shape

A clickable prototype of the key journeys and a written scope with what is in, what is out and what we are unsure about. You approve before any production code.

Build

Fortnightly releases to a staging environment you can use. Integrations are built and tested against your systems with your access, not ours.

Hand over

Documentation, admin training and an agreed support arrangement. You own the code and the data.

The full method

From field notes

Short reads for people planning a portal

Standards and limits

What we will not claim

We will not tell you a portal will raise your conversion rate or improve campaign performance. We do not manage advertising and we do not have performance data to show you. What we can say is concrete: requests arrive with the information needed, statuses are visible, approvals are recorded, and the approved file is the one people download.

We build with accessibility in mind from the first prototype, aiming for WCAG 2.2 AA, and we test with keyboard and screen reader. Personal data handling is designed with you as controller, and we will tell you plainly where a requirement needs your legal team rather than our opinion.

Equally, we will not show you logos of clients we have not served or invent numbers to make a proposal look safer. When we estimate, we give a range and the assumptions behind it, and we revisit it in writing when those assumptions change.

Standards and limits in full

Already working with us?

The help desk explains how to report a problem, what we need from you and what happens next. Support runs Monday to Friday, 09:00 to 18:00 UK time (Europe/London, GMT/BST).

Go to the help desk

Questions

Asked before every commission

Do you have an existing product we can subscribe to?

No. Each portal or workflow tool is built for the client and owned by the client. We may reuse proven open-source components and our own internal patterns, which keeps cost down, but there is no IKAME platform licence.

Can you work with our current CRM and file storage?

Usually, if they have a documented API. We confirm this early in the shaping phase by checking the specific endpoints we need, before committing to a scope.

How long does a first version take?

It depends on audiences and integrations. A focused portal with one audience and two integrations is typically measured in weeks rather than months. We give a range after shaping, not before.

Who hosts it?

Either your own cloud account, which we recommend, or a hosting arrangement we set up in your name. We avoid holding your customer data in accounts you cannot access.

Commission the next issue of your workflow.

Tell us who your portal serves and what it needs to do. We reply within two working days with questions, not a sales deck.

Start a commission