Furls turns a real problem into working software, then stays with it through production and the learning that follows. Product judgement and engineering remain one continuous practice.
The interface, code, data, content, support, release path, and day-two operation all belong to the same thing.
Furls keeps those decisions together. We can shape the proposition, map the awkward user journey, choose an architecture, write the software, prepare the service around it, and lead the route into use.
The aim is not a large specification. It is shared understanding expressed in a product people can try.
Start with the riskiest assumption and give it form. A thin prototype can put the idea in front of people, expose a technical constraint, and save months of confident guessing.
Once the signal is real, engineering broadens around it. Accessibility, security, data boundaries, observability, performance, recovery, and support are designed into the service. Production is a habitat, not a finish line.
Then the product goes live in small, reversible changes. We watch what people do, what the software does, and where the two disagree. That evidence becomes the next product decision and the next release.
Launch is when the product starts answering back. Good.
Furls builds and operates products of its own. The lessons come from users, releases, support questions, and the occasional impolite edge case.
Near Here’s free UK event discovery service collects public listings, organises them around real places, and gives people a simpler way to find what is happening nearby. Furls created the product, built the collection and publishing systems behind it, and operates the live service.
See how Furls built and operates Near Here
A familiar family muddle became a focused web application with sign-in, private household data, claim protection, and a straightforward route to self-hosting on Cloudflare. The code is open source, including the decisions below the interface that keep surprises where they belong.
Read the Family Wishlist open-source product storyThe useful starting point is the problem, not a polished brief.
Furls can take responsibility for early product definition, a rapid prototype, production engineering, a multi-team build, launch, or the next difficult phase of a product already in use.
The exact team forms around the work. What stays constant is clear product judgement, software that can stand up in operation, and responsibility that does not disappear between disciplines.
Send the honest version. The useful details are usually the ones a tidy brief leaves out.
hello@furls.co.uk↗