About
About Shakewell LLC
The Entity
Who We Are
Shakewell LLC is the United States entity of Shakewell, a full-service digital agency operating since 2018. The wider group is 45+ specialists across the United States, Australia, Asia-Pacific, and the Middle East: content engineers, technical writers, software developers, trainers, and analysts. Those are not separate departments handing work over a wall — the same teams move between structured content and software depending on what a program needs.
The US entity exists because the programs here ask for something a general digital agency cannot give them. A specification dictates the shape of the content before anyone writes a word. Review cycles assume compliance was designed in rather than inspected at the end. Delivery environments are often locked down, and the content still has to reach the people who maintain the equipment. Shakewell LLC is the part of the group organized around that reality, working with aerospace, defense, aviation, and industrial programs.
If you arrived here from the parent agency, or from a program that knows us by the group name, this is the same organization. Shakewell LLC is the group's United States entity, and the one US programs contract with.
The Practice
Structured Content Meets Engineering
Most of this market sits on one side of a line. On one side are documentation specialists, fluent in S1000D and MIL-STD-40051 but reliant on somebody else to build anything. On the other are software teams who can build the platform but treat a data module as an unusually irritating file format. Programs end up paying two vendors to negotiate the boundary between them, and the boundary is exactly where the expensive problems live.
Shakewell LLC is deliberately both. The firm that writes your business rules also builds the validator that enforces them; the people who model the content also write the code that delivers it. That is not a breadth claim, it is a cost argument — when the content model and the system serving it are designed together, most of the integration work that consumes a program's schedule simply never arises. Our services run from analysis and strategy through content engineering, training, full-stack development, applied AI, and ongoing operations, and they are meant to be used roughly in that order.
Standards as a working method
We author in S1000D, MIL-STD-40051, MIL-STD-3001, ATA iSpec 2200, ATA Spec 1000BR, ATA Spec 2300, DITA, DocBook, SGML, and W3C XML. Each has its own reference page in our standards library. A specification treated as a delivery requirement rather than a working method is where most compliance failures start.
Systems that carry the content
Structured content is worth what its delivery is worth. The Shakewell Content Portal is our own product: a distribution platform for technical publications — structured, searchable, version-controlled, and scoped to exactly who should see it. Run it hosted, in your cloud, or entirely on your own infrastructure.
The people the work lands on
A specification is adopted by writers, content architects, program managers, and the engineers whose systems feed the content. Each needs something different from us, which is why we describe the work role by role rather than as one undifferentiated capability list.
Track Record
What We Can Show You
Much of our work sits inside programs that would rather their documentation arrangements were not discussed in public, so this page names no clients and quotes no one. What we can point at is the shape of the practice: how long it has been running, how many people are in it, which specifications we actually author in, and a product that exists and ships.
- Operating since
- 2018The group has run as a full-service digital agency since 2018.
- Specialists
- 45+Content engineers, technical writers, developers, trainers, and analysts.
- Regions
- 4United States, Australia, Asia-Pacific, and the Middle East.
- Standards authored in
- 10From S1000D and the MIL-STDs through the ATA specifications to DITA and XML.
How We Work
Assess, Build, Hand Over
The engagement model is the same whether the work is a migration, a training program, or a delivery platform — and it is deliberately unflattering to our own revenue, because the goal is to finish.
Assessment before proposal
Every engagement starts by mapping the system you already have: workflows, constraints, the specification you are held to, and where the bottleneck actually sits. It is rarely where it is assumed to be. You get a clear-eyed read on where you stand before anyone quotes a build.
Build working systems
We build working systems rather than slide decks — content models, authoring environments where validation fires as you write, the integrations around them, and the platform that serves the result. Decisions get documented as they are made, so the reasoning outlives the people who made it.
Transfer the capability
Ownership goes to your team with documentation, hands-on training in the standard you actually author in, and architectures they can extend. We build real internal capability rather than permanent dependency on outside consultants. Ongoing support stays available afterwards, but it should be a choice you make, not a dependency we engineered.
Get In Touch
Let's Talk
If you're weighing up a specification, a migration, or how the content reaches the field, the earliest conversation is the most useful one.