Refract Group2026
Engineering
Built for launch day and the year after.
The front end, the back end and everything they connect to, engineered by the same team that designed it.
What you get
Software that holds up once people rely on it. We build from the design system, so what ships is what was designed, and we leave it in a state your own team can read.
- Front endFast, accessible and built from the design system’s own components.
- Back end and integrationsYour data, your APIs and the services you already pay for, connected properly.
- HandoverDocumented and readable, so your own team can keep building on it.
MCP development
Your customers are starting to use your product through AI assistants. We build Model Context Protocol servers that let Claude, ChatGPT and the rest read and act on your product safely, with the same permissions a person would have.
- ToolsThe actions an assistant can take, named and described so it picks the right one.
- PermissionsScoped to the user who asked, logged, and easy to switch off.
- TestingRun against real questions before launch, so it answers rather than guesses.
Ways to start
A product sprint
One problem, a working prototype in front of your users, and a plan for what to build next.
A project
A product, a flow or a tool, designed and built start to finish by the same team.
An embedded team
Our designers and engineers inside your sprints, on your board, for as long as it’s useful.
Questions
Ask usYes, and we prefer to. We work in your repository, your reviews and your sprints, so nothing arrives as a surprise.
Whatever suits the product and your team: usually TypeScript, Vue or React on the front, Node or Python behind it. We’ll use your stack if you have one.
If you’d like. Otherwise it’s documented and handed over so your team can run it.