Shape
We work out who the product is for, what job it does for them, and the smallest version worth releasing. You get a written product brief, sketches of key screens and a release plan with honest assumptions.
Software publisher & product studio · Guildford

Mindweave designs, builds and publishes software products — then trains the people who will use them. One studio for the whole arc, so nothing is lost between the build and the first Monday morning someone opens it.
Most software is built carefully and introduced carelessly. A launch email, a login, a link to a help page nobody reads. Then the support queue fills with the same five questions.
We treat the introduction as part of the product. The same people who shape the interface write the onboarding, plan the training and listen to what new users stumble on. The result is software that gets used the way it was meant to be used, sooner.
It also changes how we build. When the person designing a screen knows they will later have to explain it in a two-minute recording, the screen tends to get simpler. Teaching is a design discipline in disguise, and we use it on purpose.
We work out who the product is for, what job it does for them, and the smallest version worth releasing. You get a written product brief, sketches of key screens and a release plan with honest assumptions.
Design and engineering in short cycles, with something you can click through every fortnight. We favour proven, maintainable technology over novelty, and we write things down as we go.
Store listings, release notes, in-app guidance, a help centre written in your voice, and an update rhythm your users can rely on.
Training sessions for staff or customers, quick-start guides and short screen recordings — designed around real tasks rather than a tour of every button.

Good software has a feel: the way a list responds, how forgiving a form is, whether an error message sounds like a person. These details decide whether people trust a tool enough to explore it.
Tactile also means forgiving. Undo where a mistake would hurt, drafts that save themselves, and messages that say what to do next rather than what went wrong in the code.
We prototype the feel early — real interactions on real devices, not static pictures — and test them with a handful of the people who will use the product. It is the cheapest moment to learn that a clever idea is confusing.
We design training around tasks people do on a Tuesday afternoon, not features listed in a menu. Sessions are short, practical and recorded where helpful. Guides are illustrated with your real screens. We test materials with a few learners before rolling them out, and revise after the first sessions.
Training can accompany software we build, or software you already have — an internal system nobody was ever properly shown, or a product your customers find harder than they should.
Compose a training planOrganisations with an internal tool that outgrew its spreadsheet. A booking sheet, a stock list, an approvals inbox that now needs to be a proper application with permissions, history and a help page.
Specialists turning know-how into a product. Trainers, consultants and small firms who want to publish a focused tool for their clients, with the documentation and onboarding to match.
Teams whose software works but is not used. The system was delivered; adoption never followed. We redesign the confusing parts, write the missing guidance and run the training that should have happened at launch.
Founders preparing a first release. People who need a small, well-built first version in the stores or on the web, released properly and explained clearly, rather than a sprawling prototype.
Most first releases we plan take a few months from the end of discovery, though the honest answer depends on scope, integrations and how quickly decisions are made. The rhythm is consistent. Discovery produces the brief and the shortlist of screens. Design turns those screens into an interactive prototype we test with real people. Build runs in fortnightly cycles, each ending with a version you can try on your own device.
Publishing work starts alongside build, not after it: help articles are drafted as features settle, store listings are prepared while the last cycle runs, and the training plan is shaped by what testers found difficult. On release day the product, its documentation and its first training session are ready together. Then we watch the first weeks closely, collect the questions people ask, and fold the answers back into the product and its guides.
No ready-made product to sign up to. We build and publish software for clients, and may publish our own tools in future. There are no existing Mindweave accounts or logins today.
Training is practical, not accredited. We do not issue certificates or qualifications. People leave able to do their work.
Your code, your accounts. Repositories, app store accounts and hosting are set up in your name from the start.
Clear limits. We do not offer round-the-clock support, and we will tell you when an off-the-shelf tool would serve you better than something bespoke.
We are a focused studio. We do our best work on products where a small team can hold the whole thing in its head: a first release in months, not years. For larger programmes we can lead discovery, design and training alongside your engineering partners.
No. We also improve existing software — redesigning confusing areas, writing missing documentation, and training users who were never properly introduced.
On payment, you own the code, designs and written materials made for you. We retain only general know-how and any open-source components, which remain under their own licences.
Discovery is a fixed fee. Build and training are estimated per phase after discovery, with a ceiling you approve before each phase starts.
Describe who will use your software and what they need to get done. We will reply within two working days with questions and a suggested first step.
Write to us