digitala. Portals Consulting Write to us

Digital solution consultancy & web portals · London

Portals that people understand the first time they open them.

A dark tablet resting on deep ultramarine velvet beside a twist of pink glass
Illustrative image

Digitala Development is a digital consulting studio. We help organisations decide what their digital service should actually say and do, then design and build the web portals where their clients, members, partners and staff find answers for themselves.

We start with communication, not features: who is on the other side of the screen, what they are trying to find out, and what your organisation needs to tell them. The technology follows from that.

Write to us Sketch a portal

A note before the details

Most digital problems are conversations that went wrong.

A client emails three times because a status was never shown. A member calls because the renewal page uses a word only your finance team understands. A partner keeps a private spreadsheet because your system cannot tell them what has been agreed. None of these are technical failures. They are failures to communicate, which happen to live in software.

That is why we work the way we do. We listen to the people who use your service and the people who run it, we write down what each needs to know, and only then do we propose a solution. Sometimes that is a new portal. Sometimes it is a smaller change to something you already have. Occasionally it is a better email template and no new software at all, and we will tell you so.

— The Digitala studio

Two practices, one studio

Digital consultingDiscovery, service mapping, requirements, supplier and platform choice, content structure. For when you know something is wrong but not yet what to build. Web portalsSecure, accessible portals for clients, members, partners and staff, connected to the systems you already use. Designed, built and supported. Portal plannerA short interactive outline: choose your audiences and what they need, and receive a first written sketch of the portal.

Three questions

What is your audience actually asking?

Every portal we design starts from the handful of questions its users bring to it. Choose an audience to see where we usually begin.

  1. Where is my request, and what happens next?
  2. What do you need from me, and by when?
  3. Where are the documents you have sent me?

If your portal answers these three questions for clients without an email, it is already doing most of its job.

Portals, in one paragraph

What a web portal is for

A portal is a promise that the answer is somewhere, and that it is the same answer your staff would give.

A portal is not a website with a login added. It is a private, personalised space where someone outside or inside your organisation can see what relates to them, act on it and trust what they see. Done well, it reduces routine email and calls, removes version confusion and gives people a calm sense of being looked after. Done badly, it becomes another inbox nobody checks.

The difference is rarely the platform. It is the clarity of the words, the order of the information and whether the portal reflects the real state of things, not a copy updated by hand on Fridays.

How a project unfolds

Four conversations

  1. Listening

    We meet the people who run the service and, where possible, the people who use it. We read the emails, forms and help pages that exist today.

  2. Shaping

    We write a short service outline: audiences, their questions, the information and actions the portal must offer, and what is deliberately left out.

  3. Making

    Design and build in short rounds. You review real screens with real wording, not abstract diagrams, and we adjust as we go.

  4. Looking after

    Launch, training for your administrators, and support during UK working hours under a written arrangement.

Read about each conversation

Deliverables

What you receive

A service outline
Plain-language description of audiences, their questions and the portal’s responsibilities. Useful even if someone else builds it.
Content structure and key wording
Navigation, page purposes and the critical messages: statuses, errors, confirmations, emails.
Designed and built portal
Accessible interface, secure sign-in, roles and permissions, connections to your existing systems where agreed.
Administrator guide
How your team updates content, manages users and handles common requests.
Handover pack
Hosting and running costs, source code in your repository, credentials in your accounts.

Quality

What good looks like

  • Words people understand. Every label and message tested against the question “would a new user know what this means?”
  • Accessible by default. Keyboard use, screen readers, contrast and clear focus, checked against WCAG 2.2 AA criteria.
  • Honest states. Nothing shown as complete that is not; nothing hidden that a user needs.
  • Minimal personal data. We collect what the service needs and agree retention with you.
  • Something your team can run. Content and users managed without calling us.
Our standards in full
Pink iridescent glass ribbon on ultramarine fabric

Where we stop

Clear about our limits

We are consultants and portal builders. We do not provide round-the-clock operations, legal or regulated advice, hardware, or marketing campaigns. We will not claim a platform can do something until we have seen it do it. When a need falls outside what we do well, we say so and point you to the kind of specialist who can help.

We are also a young company. We do not show client logos or invented case studies; we would rather show you how we think in a first conversation.

Support

Help after launch

Portals live alongside a changing organisation. After launch we offer support during UK working hours, Monday to Friday, with acknowledgement within one working day, a clear distinction between fixes and changes, and periodic reviews of how people are actually using the portal so we can improve its wording and structure.

Help and support requests

Questions

Questions we hear often

Can you work with our existing platform?
Often, yes. Many organisations already have a CRM, membership or case system that can feed a portal. We assess it during the first conversation and say plainly if it will help or hinder.
How long does a portal take?
A focused first release is commonly eight to fourteen weeks after the service outline is agreed. Larger scopes are split into releases.
Do you write the content?
We write the structural and functional wording: labels, statuses, messages, emails. We can help shape longer content, but your experts should own it.
Who owns the code and accounts?
You do. Everything is set up under your organisation’s accounts from the start.
Can we start with consulting only?
Yes. Many projects begin with a short consulting engagement, and the outline is yours to take to any supplier.

Write to us as you would to a colleague.

Tell us who your service is for and what is getting lost. We reply within two working days, with questions or a suggested next step.

Write to us helpme@digitaladev.org