Websites & interfaces
We design and build public websites, customer portals and product interfaces. The aim is to help people understand the offer, complete a task and know what happens next.
Explore websites & interfacesIndependent applied AI, design & engineering
About 6 Watt Labs
6 Watt Labs is an independent software studio that builds websites, automations, internal tools and private AI systems for research teams, business operations and delivery partners.
We work from the problem through to the interface, the systems behind it and the handoff. You work directly with the people responsible for the result.
What we build
A useful system starts with what someone needs to get done. We choose the tools around that.
Automations & integrations
We connect tools and reduce repeated handoffs, from collecting a request to preparing a report. Each workflow has a defined trigger, an owner and a way to handle exceptions.
Explore automationsDashboards & internal tools
We build software around the decisions your team needs to make. Project rooms, review queues and dashboards bring the relevant information and next action together.
Explore internal toolsApplied AI & private systems
We use AI where interpreting information helps a real workflow, with evaluation against examples from the task. Data access, permissions and decisions that need a person are agreed as part of the design.
Explore applied AIWhat you can expect
We agree the work and how you will review it before we build.
Design and engineering together
We work on the experience people see and the systems that support it. Interface decisions can be checked against the actual workflow, data and permissions.
Decide what to build first
A technical decision review or systems roadmap can come before a production build. We agree the outcome, scope, price and review points before implementation begins.
Review against agreed criteria
Acceptance criteria are agreed with you, then checked against the work. Drafts, feedback and decisions stay connected to the version being reviewed in your project workspace.
Our team is responsible for delivery
Agents help us research, design, implement and check. Our team remains responsible for the decisions and delivery; AI belongs in the finished product only when it serves the problem.
Handoff and ongoing care
Files, access, documentation and ownership are part of the delivery conversation. Where ongoing care is needed, we agree its scope, responsibilities and terms separately.
Who we work with
A clear problem and someone who can review the result matter more than a finished specification.
Research & scientific teams
Teams working through literature, data, analysis or manuscript workflows who need reproducibility, visible evidence and researcher review.
See illustrative research workflowsBusiness operations teams
People moving information between tools, maintaining a spreadsheet workaround or repeating a reporting and approval process.
Map your workflowDelivery partners
Teams that need technical capacity for a defined piece of client work, with agreed responsibilities and review points.
Discuss a partnership
The team
Our approach combines software engineering with evaluation against real tasks: what should the system do, and what evidence would show that it works?
We are a small, independent studio. You work directly with the people responsible for your project, from understanding the problem to reviewing the result.
Working together
See the full project processStart with a brief
Describe the problem, how the work happens today and any constraints through Start a project. The receipt includes a private status link, so you can check your enquiry before you have a client account.
Agree the working arrangements
We agree scope, price, timing, review points and responsibilities before building. Communication channels, update frequency and response expectations are set for the engagement; there is no blanket turnaround or response-time promise.
Review in a shared project space
Once we agree to work together, you are invited to a private workspace for scope, updates, review feedback, decisions and delivery files. We bring the handoff and any ongoing care arrangement together before the project closes.
Key facts
Services, access and project arrangements.
- Studio name
- 6 Watt Labs, also styled 6WLabs.
- Type
- Independent applied AI, design and engineering studio.
- Core offering
- Custom software built around a defined workflow, from the first technical decision through delivery and care.
- Services
- Websites and interfaces; automations and integrations; dashboards and internal tools; applied AI and private systems.
- Intended clients
- Research and scientific teams, business operations teams and delivery partners.
- Our approach
- Applied AI engineering and evaluation against agreed criteria.
- Engagements
- Technical decision review, systems roadmap, production build, and care and stewardship.
- Pricing & terms
- Scoped and priced individually. Scope, timing, price and review points are agreed before implementation; ongoing care is separately defined.
- Communication
- Enquiry and receipt first; an invited project workspace for agreed work. Other channels and response expectations are agreed per engagement.
- Website & contact
- 6 Watt Labs website · Send a project brief · Privacy & contact details
Questions before you start
Do I need a finished specification?
No. A short explanation of the problem, an example of the current workflow and the people involved are enough to begin. A decision review or roadmap can help clarify what is worth building.
How much does a project cost, and how long does it take?
Both depend on the outcome, existing systems, access and constraints. We scope and price the work with you, and agree timing and review points before implementation.
Does every project need AI?
No. A website, a conventional integration or a simpler piece of software may be the right answer. When AI is useful, we agree how to evaluate it and where a person needs to review its output.
Can you work with our existing tools or private infrastructure?
We assess supported APIs, permissions, data quality and failure handling before promising an integration. Private or customer-owned deployment can be considered when control matters, with access and operating responsibilities agreed in scope.
What happens after delivery?
Each project has an explicit handoff and ownership plan. Care and stewardship can cover agreed maintenance, monitoring, adoption support and improvements; the boundaries are defined with you.
Tell us what needs to work better
A rough idea, a recurring workaround or a specific brief is a useful start.