The 9-to-5 had run its course. Not the work. The shape of it. Almost twenty years in IT, frontend, and the messy overlap between them. Government platforms. Healthcare systems. Enterprise dashboards that people quietly hate. You see the same problem often enough, in enough industries, and it stops being a coincidence and starts being the thing.
So I took a proper break. Not the sort where you announce on LinkedIn that you are “taking time to recharge” and then post three motivational quotes about vulnerability. The sort where you sit down with a coffee, no calendar, no standup, no roadmap, and ask what you would actually build if you were not answering to somebody else’s.
The lazy answer was ‘go freelance’. Print cards. Build a portfolio site. Say yes to everything. Wait for referrals.
That was not the answer.
I need to build the thing properly. Which meant, awkwardly, starting where every practice worth taking seriously starts. Not with a domain. Not with a services page. With an idea that survives being written down.
I gave myself the same treatment I would give a client. What is this for? Who is it for? What does it refuse to be? What does it look like when it turns up in a room?
The name came first. Logias. From logos: “word, reason, study“. It had to sound like a place that thinks before it draws, not a place that draws while thinking about drawing. It could not sound like a start-up that believes it invented the word “platform”. It could not sound like a boutique agency named after a Scandinavian furniture designer nobody has heard of. It had to sit on a business card next to the word “consultancy” and not embarrass itself.
Then the visual identity. Paper and ink. A confident red as the accent. A yellow that behaves itself. Lexend for the headers because it was designed for reading proficiency, and if a UX consultancy cannot practise what it charges for on its own wordmark, the whole thing is a joke. Zalando Sans for the body. An asterisk as the monogram, because the annotation mark is the honest symbol for what this work actually is. Somebody in the margin is taking notes, writing “Look at this bit again.”
The colours took an afternoon. The name took a week. The posture took the longest, and the posture was the thing. Because a consultancy is not a logo file. It is a way of behaving. And behaviour has to be decided before the website tries to explain it, or the website becomes another polished object apologising for a business that has not been thought through.
That is the part most consultancies skip.
They begin with the artefacts and hope the thinking will arrive later. Colours. Typefaces. A logo file named final-final-actually-final.svg. A declaration that the business is “a full-service creative agency”.
That is how you end up with a polished website explaining that you are available for anything. UX. Websites. Logos. SEO. Social media. Marketing. Branding. Probably drone footage by Friday.
I can do a lot of those things. That was not the question.
The question was: what is Logias actually for?
The thesis
I have watched enough otherwise competent organisations tie themselves into a knot over the same thing. A website looks dated. A dashboard is confusing. An internal tool is slow, inconsistent, inaccessible, or just deeply irritating to use.
Then somebody asks for a redesign.
Sometimes they are right. More often, the interface is simply where the failure finally became visible. The real problem started earlier. Nobody properly understood the people using the thing, the decisions they make, the constraints around them, or the work they are actually trying to complete. So the product was built around assumptions, stakeholder preference, a rushed requirement, or whatever survived the meeting.
Then it gets handed to a designer, and everybody looks at the buttons.
That is the gap Logias exists to deal with.
Products fail because the workflow was never understood, not because the code was ugly or the interface was unfashionable. The interface still matters. Code still matters. Accessibility very much matters. But none of it starts with picking components from a library and making them rounder.
It starts with studying the work. What is the user trying to do? What information do they have at the moment they need it? What are they afraid of getting wrong? Where does the process collapse? What has the organisation quietly accepted as “just how it works”?
That is the work before the work.
The name comes from logos: word, reason, and study. Logias is not meant to sound mystical, expensive, or like a start-up that believes it invented the word “platform”. It describes the posture. Study the thing properly. Make the argument. Then build what the evidence supports.
We are always studying.
A company is not a list of services
The first version of almost every consultancy sounds like this:
“We provide UX design, web development, graphic design, social media, SEO, branding, marketing strategy, content creation, digital transformation, and, somehow, possibly coffee.”
Technically, that is a business model. It is also a fairly good way to become impossible to remember.
A buyer should be able to explain what you do after leaving your website. Not repeat every capability. Explain the point.
Logias has one spearhead: accessibility assessment and remediation guidance. That is the front door because it is a real business need, a defined engagement, and something public-sector and enterprise buyers can procure without having to translate “we need somebody good at UX” into a scope of work.
There is no magical compliance sticker at the end of it. There is no widget that gets installed in the footer, plays a little animation, and transforms a broken product into a responsible one. Anybody selling that is selling a shortcut to a problem they have not read properly.
The underlying work still has to be examined. Forms. Keyboard paths. Focus behaviour. Semantics. Documents. Error states. The flow a person follows when they are trying to get something done.
The workflow. There it is again.
Accessibility as the bread
Accessibility is not a side offering because it is not a side concern.
It affects whether somebody can complete an application, understand a bill, book an appointment, submit a form, or do their job. It also reveals the general health of a digital product. A product that is difficult to use with a keyboard, confusing with a screen reader, built from meaningless markup, or full of unreadable contrast decisions usually has other problems too. It is rarely the only thing wrong. It is simply the thing that cannot be waved away as taste.
That makes it the right spearhead. It leads naturally into UX consulting: if an audit finds that a person cannot complete a task, the answer may be a semantic correction. It may also be a broken workflow, unclear content, a bad approval process, an unnecessary field, or a decision that was never made. Somebody has to discover which. It also leads naturally into development, because recommendations are worth considerably more when the person making them understands what it takes to implement them without turning the codebase into a mess by Wednesday.
Everything else is secondary. Search visibility can be part of a web engagement. Design concepting can be part of an engagement. A brand system may need to be clarified before the interface can be made coherent. Those are real needs. They do not need to pretend they are the main character.
Social media management is not part of the model. Native app work is not part of the model. I am not putting either on a services page and then discovering six months later that I have accidentally become responsible for somebody’s Tuesday afternoon Instagram caption about National Doughnut Day.
Life is already complicated enough.
The work Logias will refuse
A business becomes clearer when it states what it will not do. Not as theatre. Not as an attempt to sound difficult on the internet. A boundary is useful when it protects the quality of the work and tells the buyer what kind of relationship they are entering.
Logias will not install accessibility overlays. An overlay does not repair the product underneath it. It does not replace accessible structure, accessible content, tested interactions, or responsible engineering. It is a shortcut sold to people who have been told the problem is too complicated to understand. The problem is complicated. That does not make the shortcut real.
Logias will not produce rubber-stamp audits. If the work cannot be properly reviewed, the report should say so. If testing finds no problems at all, everyone involved should be more cautious, not less. A useful audit tells the truth about the system that exists. It is not there to make a buyer feel better about a decision already made.
Logias will not skip discovery when discovery is the work. If an organisation has already decided the answer, already chosen the design, already selected the implementation, and merely needs a pair of hands to produce it, there are contractors for that. Good contractors. That is a different engagement.
And Logias will not run design by committee. Stakeholders should provide goals, constraints, institutional knowledge, and the things they know that no external consultant could possibly know. They should be heard properly. But a screen does not become better because fifteen people were allowed to vote on the shade of blue. Someone must own the decision. Someone must explain the rationale. Someone must be accountable when the thing goes live.
That is not arrogance. It is basic operational hygiene.
Proof has to be built
A new consultancy has an obvious problem: it needs evidence before it has a long list of consultancy clients.
The underlying career already covers the ground. State public-health platforms at scale (CDPH CAIRHub). Defence-adjacent hardened container work (Platform One / Iron Bank). Healthcare-adjacent tooling that had to survive real audits from real people. Those show up as case studies, framed around the client problem and the outcome, with attribution and disclosure handled properly. They are the track record. They are not the pitch.
The pitch is the published teardown. A real product or service, studied against accessibility and UX criteria, with documented findings, annotated evidence, and recommendations that show the work as it would be delivered in a proper engagement. No claim that the organisation is universally non-compliant. No fake client relationship. No “here is what I would do if they had hired me” performance.
Just the work.
The teardown becomes the sample audit. The sample audit becomes the content engine. The content engine gives people a reason to encounter Logias before they need Logias.
That is a much better beginning than waiting around for somebody to grant permission to have a point of view.
Who this is for
Logias is based in western Massachusetts and serves the Springfield, Hartford, Boston, and Albany corridors, alongside remote US clients.
The first audience is public-sector and enterprise buyers with an accessibility requirement, a procurement process, and a need for work that can be explained in plain language. They will read closely. They will print things. They will check whether the business seems real. Fair enough.
The second audience is founders and small organisations who have reached the point where their website, application, or service flow is no longer something they can keep patching at night. They may arrive through a referral. They may read quickly. They still need the same answer: does this person understand the problem, and can they carry the work through?
The third audience is other accessibility and UX professionals. They may never become clients. They will be part of the referral engine, the professional conversation, and the reason the teardown work needs to be rigorous enough to survive somebody knowledgeable reading it with their arms folded.
That is the business. Not a creative agency for everything. Not an aspirational company waiting to decide what it does. Not a nine-to-five with a different logo on it.
A consultancy with a clear front door, a point of view about the work, and enough technical depth to build what it recommends.
Now it needs a form.