web portals and IT services / London W1
People on one side. Information on the other. A route between.
ONEKUK designs, builds and looks after web portals: the places where staff, members, suppliers or customers go to find what they need, ask for something and see what happens next. We start with the people and the questions they arrive with, not with a template of widgets.
intranetsmember and supplier portalsdocument librariesrequest routesongoing IT care

definition
What we mean by a portal
A portal is a front door with a floor plan: one place, recognisably yours, that sends each kind of visitor to the information and actions meant for them.
It might be an intranet for a team of forty, a members' area for an association, a supplier site where invoices and specifications live, or a customer page where requests are made and tracked. What they share is a problem of organisation. The content usually exists already, spread across shared drives, inboxes and old websites. The work is to decide who needs what, in which order, under which words, and who keeps it accurate.
ONEKUK Ltd is registered for web portal and other information technology service activities. We do both halves: we build the portal, and we provide the IT services that keep it working, secure and current afterwards.
who arrives
Start with the people at the door
Every portal serves more than one audience, and each arrives with a different question and a different level of patience. Naming them is the first piece of design.
Staff
Need policies, forms and the right colleague, quickly, between other work.
Members
Want their own records, events and updates, without ringing anyone.
Suppliers
Look for specifications, payment status and who to ask.
Customers
Want to make a request and see where it has got to.
the usual state of things
Information that exists but cannot be found
Three copies of one policy
The current version is on a shared drive, an older one is on the intranet, and a third is attached to an email everyone forwards. Nobody is sure which is right.
Menus shaped like the organisation chart
Sections are named after departments, so a new starter has to know who owns holiday requests before they can find the form.
Requests that vanish
A web form sends an email to a general inbox. The person who filled it in never hears whether it arrived.
An intranet no one updates
The original builder has moved on, nobody owns the pages, and the news section stopped two years ago.
Access by guesswork
Former suppliers still have accounts, and current ones are sharing a single login because adding users is awkward.
Search that returns everything
Typing "leave" brings up 140 results, most of them meeting minutes, and the form itself is on page four.
services directory
What ONEKUK does
APortal discovery and structure
Short interviews and task reviews with each audience, an inventory of existing content, and a proposed structure organised around tasks. You receive a site map, a label list and an ownership table before anything is built.
BPortal build
We build the portal on a platform chosen for your situation, which may be one you already pay for. Pages, document libraries, request forms, search and audience-specific areas are configured to the agreed structure, with accessibility treated as a requirement rather than a polish step.
CInformation and content structure
Metadata, naming conventions, document templates and review dates, so that content stays findable after launch. We help you migrate what should move and retire what should not.
DAccess and permissions
A simple, written model of who can see and change what, how new accounts are approved and how leavers are removed. The model is designed to be maintained by you, not only by us.
EOngoing IT services
Updates, backups checks, user administration, fixes and small changes, carried out during UK working hours under an agreed arrangement. Details are on the IT services page.
FReview of an existing portal
A structured look at a portal you already have: what people use, where they get lost, what is out of date and what is risky. You receive a prioritised list of changes you could make with or without us.
one journey, followed
From question to answer, in five stops
A supplier wants to know whether an invoice has been paid. Here is the route a well-organised portal gives them, and the decision behind each stop.
Arrive
The supplier signs in and lands on a page written for suppliers, not on the staff home page.
Recognise
"Payments and invoices" is one of five plainly worded options. No acronyms, no department names.
Find
Their submitted invoices are listed with status. If status data cannot be shown, the page says who to ask and how soon they will reply.
Ask
A short request form goes to a named team queue, with an automatic receipt and reference.
Hear back
A reply arrives within the promised time. The page that triggered the question is improved if it was unclear.
tool c
Plain label checker
Paste the menu or section labels you are considering, one per line. The checker flags internal jargon, acronyms, vague words and duplicates that tend to make people hunt.
try it now
Are your labels doing their job?
Most portals are hard to use because of the words on the buttons. Paste your current menu and see which labels describe a place instead of a task. Two more planning aids are on the tools page: an audience and task mapper and a content review sizer.
after launch
The IT services that keep a portal honest
A portal starts decaying the day it launches unless someone looks after it. Our IT services cover the unglamorous, essential work: applying updates, checking that backups exist and can be restored, adding and removing users, fixing broken links and forms, and making small changes as your organisation changes.
This work is done during UK working hours, Monday to Friday, under an arrangement agreed in advance. We do not offer round-the-clock monitoring or emergency call-out, and we will tell you if your situation needs it so that you can plan accordingly.
how we work
Four phases, each with something to hold
Listen
Interviews, task lists and a look at existing content. Output: audience and task map.
Arrange
Structure, labels, ownership and access model. Output: site map you approve.
Build
Configuration, migration and testing with real users from each audience. Output: working portal.
Look after
Handover, training for content owners, then ongoing IT services if you want them.
plainly
What we do not promise
- We do not claim partnerships with, or certifications from, any software vendor. We will recommend platforms on their merits for your case.
- We do not run physical data centres. Hosting is arranged with established providers and named in your agreement.
- We do not offer 24/7 monitoring. Support is Monday to Friday, 09:00 to 18:00 UK time.
- We do not list clients or quote figures from past work on this site. We would rather show you our thinking on your own problem.
- A portal cannot fix a process nobody owns. If ownership is missing, we will say so before building.
guides
Reading before you commission anything
Our guides cover writing labels people understand, deciding who owns which content, planning access for external users, and what to ask any portal supplier, including us. They are written to be useful even if you never get in touch.
Labels
Name the task, not the department.
Ownership
Every page has a person and a review date.
Access
Decide who approves accounts before launch.
Questions
Ten things to ask a portal supplier.
get in touch
Tell us who needs to find what
A useful first message says who the portal is for, what they currently struggle to find or do, and what exists today. No technical specification is needed.
Existing clients can raise problems or changes through support.
Monday to Friday, 09:00 to 18:00, Europe/London.
ONEKUK Ltd, company number 17082958
Registered office: 85 Charlotte Street, London, England, W1T 4PS