Skip to content

[ 01 ] MA thesis · Voice AI · Physical computing

NCAD Dublin / 2026

University
NCAD, Dublin
Year
2026
Team
1 person
Duration
12 weeks

Lugh

A voice-first AI agent for the workshop.

Lugh at work, in a maker's studio

[ In one line ]

A voice-first AI agent for independent craft makers in Ireland, handling the administrative work without asking for a screen.

01

Overview

A project about craft, admin, and where work gets done.

Lugh takes on the administrative side of running a small craft practice (email, quoting, time and materials, opportunity hunting) without asking the maker to leave the bench.

Developed at NCAD as my MA thesis, it includes primary research with working makers, an agentic system built on Claude and n8n, and a physical device made in the workshop.

02

Starting point

A sector that is economically significant and personally fragile.

63,000People employed
€11.3BAnnual turnover
88%Sole traders & micro-enterprises

Irish craft employs around 63,000 people and turns over €11.3B a year, but 88% of it is sole traders and micro-enterprises. Across the UK and Ireland, average craft income is under £20,000, with more than half of makers earning less than £10,000.

The gap between those two sets of numbers is where the project starts.

03

Research

The entrepreneurial burden of the practice.

15 in-depth interviews, 20 to 40 minutes each, with craft makers and craft institutions. Working makers described two roles running from one pair of hands.

The craft was the one they had chosen and trained for. The business (quoting, invoicing, chasing open calls, tracking what a piece cost) arrived unasked and without preparation, taking its time from the same working day.

“The admin doesn't sit alongside the practice. It comes out of it.”From the maker interviews

A maker reading printed papers at her desk, her studio shelves and tools around her
01 In the studio: the admin arrives at the same desk as the work.
A shared workshop with a bandsaw, workbenches and tools on the wall
02 Where the day is actually spent.
04

Key insight

The problem isn't the admin, it's the context.

The screen is the interruption. Opening an app isn't neutral, it's a context switch. It pulls attention away from the material, and the return isn't free either: notifications, tabs, everything else competing for the same glance. The problem isn't the difficulty of the task. It's where it forces the maker's attention to go.

Step 01A notificationThe maker checks the phone.
Step 02Eyes and hands leave the workThe mindset switches.
Step 03Other inputsDistraction, and the workflow breaks.
Step 04Back to the benchRe-entering focus takes energy and time.

How might we

How might we support Irish craft makers with the administrative demands of running a practice, without asking them to leave the workshop for a desk-based, screen-first workflow?

05

The concept

An agent you talk to, that never asks you to look at anything.

A single voice agent, Lugh, delivered through two touchpoints: a wearable clip that captures the maker's voice, and a walnut-finished wood dock that lives in the workshop, speaks back, and signals its state through ambient light. Every interaction is entirely screenless.

Claude sits at the centre as the reasoning layer, connected to Gmail, Drive and n8n to carry out what's asked, while a dashboard brings together everything gathered along the way for the moments the maker does sit down.

The Lugh vocal AI agent icon: an ivory starburst on a terracotta rounded square
03 Vocal AI agent.
The Lugh dock: walnut-stained wood, two round eyes, a clip microphone on the side
04 Physical dock station.
The Lugh dashboard open on a laptop
05 Online dashboard.
06

The system

Claude decides what should happen. n8n does it.

Layer 01ReasoningClaude interprets the request, works out which action it maps to, and decides when to confirm rather than act. It reaches every service through MCP, choosing the connector and parameters itself, with no glue layer translating intent. Local models were considered and rejected: they don't yet reason reliably enough for this.
Layer 02TriggerA Vosk model listens locally to audio captured through pyAudio, watching for the wake word and turning speech into text. Nothing leaves the machine until it's heard.
Layer 03DeliveryPlaywright fills the chatbox with the request and reads Claude's reply back out; ElevenLabs turns that text into audio and plays it.
pyAudio captures the maker’s voice Vosk hears the wake word and turns speech into text Playwright fills the chatbox with the request ElevenLabs turns the reply into audio and plays it Claude
06 The voice loop: pyAudio, Vosk, Claude, Playwright, ElevenLabs.
Google
Sheets
Gmail Google
Calendar
Google
Drive
07 n8n and the services behind it.

Each n8n workflow is triggered by Claude through MCP and backed by Google Sheets, keeping the system inspectable outside the agent. Calendar and Gmail skip n8n entirely: both are reached through Claude's native MCP connectors, since they already expose the exact actions needed as structured tools.

WorkflowRouteWhat it does
Time trackingn8nStarts, stops, pauses or resumes a timer; pausing and resuming let a maker step away and pick the same timer back up rather than restarting it
To-do listn8nAdds a task, marks one done, or lists pending tasks formatted to be spoken aloud
Opportunities findern8nRuns on a daily schedule rather than on request. Pulls listings from DCCI, Feltmakers and OLIST, merges and deduplicates them, and saves only new entries
Accountability: data entryn8nLogs new projects, costs, revenues and fixed costs
Accountability: data queryn8nReads that data back, from a project summary to a running list of fixed costs
Invoice generationn8nFills a Drive template with company and invoice details, exports it as a PDF, and logs the new invoice
CalendarMCP (Claude)Checks today’s schedule, creates or updates events
GmailMCP (Claude)Reads a message, drafts a reply, sends once confirmed
08 Every workflow, its route, and what it does.

The split is invisible to the maker. Both routes are the same spoken exchange with the same agent.

07

The dock

Built as a workshop tool, not a tech object.

Pine, mitred at forty-five degrees so the seams disappear, walnut stain, fabric over the speaker and the acrylic eyes. Speaker, micro:bit, battery and LED rings under a removable face, running with no cables at all.

Cutting the pine on a table saw in the NCAD workshop
09 Cutting the pine on the table saw.
The mitred front frame and face panels, cut and laid out
10 The parts, mitred.
The face panel with the two eye holes cut, standing on the bench
11 The face, eyes cut out.
The dock frame glued and clamped, walnut stain drying
12 Glued, clamped, left to dry.
The stained box with the face on, before the speaker goes in
13 Stained, before the speaker.

Closer to a small robot than a speaker. An object with a face asks for permission more honestly.Makers are protective of their space

What the eyes say

01Standby Dock eyes glowing yellow, standby state

A yellow light pulses very slowly.

02Listening Dock eyes glowing orange, listening state

The light is orange, and it blinks more frequently, alternating between the two eyes.

03Processing Dock eyes with a chasing orange light, processing state

A single orange LED chases around the ring, like a loading spinner.

04Responding Dock eyes glowing green, responding state

The light turns green and pulses.

08

The dashboard

A secondary support, not where the work happens.

The primary workflow belongs at the bench. But the agent accumulates things worth looking at, and every maker eventually sits down. Every section traces back to a research finding: the pricing uncertainty that kept coming up in interviews produced both the time tracking and the accountability section.

Beyond checking in, the dashboard is where the maker can review what the agent logged and correct it by hand: fixing an entry, editing a record, or entering something the agent missed.

[ Site map ]

Voice Agent Dashboard

Topbar · Navigation · Profile · Settings

01

Dashboard

Home · Overview
  1. 1.1

    Greeting

    Dynamic greeting message

  2. 1.2

    Opportunities preview

    Visibility · Grants · Others columns

  3. 1.3

    Calendar widget

    Month grid, selected day and session count

  4. 1.4

    To-do widget

    Preview of pending tasks

  5. 1.5

    Hours chart

    Hours-worked ring + legend

  6. 1.6

    Accountability rings

    Costs / revenue rings with month navigation

02

Actions

Hub: workspace picker
  1. 2.1

    Accountability

    • Tabs: Projects · Costs · Invoices
    • Costs: fixed/variable, filter, export
    • Invoices: list + income toggle
    • Edit-project modal
  2. 2.2

    Calendar

    • Month / Week view
    • Day grid + events
    • Upcoming events
    • Month navigation
  3. 2.3

    To-do list

    • High / Medium / Low columns
    • Task-completion checkboxes
    • Previous (completed) list
  4. 2.4

    Communications

    • Main list
    • Starred list
    • Instagram, Gmail, WhatsApp navigation bar
  5. 2.5

    Time manager

    • Tabs: Stats · Tasks · Projects
    • Period: Week / Month / Year / Custom
    • Task & project charts
    • Min/max stats per task & project
  6. 2.6

    Opportunities

    • Visibility · Grants · Others columns
    • Starred / Past filters
    • Per-site filters
    • Archive opportunity
03

Agent

Voice assistant: Lugh
  1. 3.1

    Chat with Lugh

    • Message thread
    • Text input field
    • Send message
    • Voice input (microphone)
  2. 3.2

    Quick actions

    • “Give me an overview”
    • “New project”
04

Extensions

Google integrations
  1. 4.1

    Gmail

    • Connection status
    • Detail panel
    • Recheck connection
  2. 4.2

    Google Calendar

    • Connection status
    • Detail panel
    • Recheck connection
  3. 4.3

    Google Sheets

    • Connection status
    • Detail panel
    • Recheck connection
  4. 4.4

    FAQ

    • Why share Sheets with a service account?
    • Why did Gmail/Calendar stop working?
    • What is n8n and why does it matter?
    • Is everything here data?
    • How do I revoke access later?
  5. 4.5

    Video walkthrough

    • How to connect Gmail, Calendar, Sheets, n8n
    • Onboarding help
14 4 navigation sections · 6 Actions workspaces · 5 Extensions cards

Wherever a card shows data from Gmail, Calendar or Sheets, an “Open in Gmail”, “Open in Calendar” or “Open in Sheets” button sits beside it. The dashboard was built to complement those tools, not replace them, so a maker who wants the real thing is always one click away from it.

Dashboard home: “Good afternoon, Ludovico”, with calendar, to-do list, email and accountability cards
15 Home: the day at a glance.
Accountability page: earnings, costs and project totals
16 Accountability: what a piece really cost.
09

The branding

A palette drawn from the object itself.

Lugh, the Irish god of crafts and master of every trade. A name from the tradition, not the technology.

The identity was drawn out of the object rather than applied to it. The logo is a minimal side profile of Lugh, holding out the microphone.

Ivory#FBF1E5The light in the eyes
Terracotta#BB6C43The stained timber
Plum-brown#4B403BThe speaker fabric
The Lugh wordmark in terracotta on ivory
17 The wordmark.
The Lugh icon mark: a minimal side profile holding out a microphone
18 The icon: Lugh's side profile, holding out the microphone.
10

Testing

Three rounds, alongside three prototype stages.

Round 01Non-makersExposed the core problem of voice: written answers get tedious once they're spoken, not read. Responses were rewritten short.
Round 02Working makersSurfaced what only working makers could find: the timer needing to pause rather than just stop, the dashboard needing to be editable rather than passive. The gaps that only show up when the person testing actually knows what a day at the bench feels like.
Round 03RefinementNot discovery: wake word phrasing, the processing sound, small friction that only becomes visible once the bigger pieces are already working.
A maker at her kitchen table talking to the dock, a laptop beside her
19 Testing at home.
A tester at a workbench with the dock and a laptop
20 Testing on the bench.
A ceramicist holding the Lugh dock in her studio
21 Testing with working makers, in their own workshops.
11

Final design

Lugh.

The finished dock from the front-left, the clip microphone docked on its side
22 Front, with the clip docked.
The finished dock from behind: plain walnut-stained wood
23 Back, no cables.
The finished dock from the side, the microphone and the speaker fabric
24 Side, microphone and speaker.
The finished Lugh dock on a wooden table, microphone clipped to its side
25 The final object.
12

Reflections

Next steps.

The dock itself could be tailored to the maker, proportions and materials adapted to a ceramicist's studio, a leatherworker's bench, a jeweller's desk, so the object fits the practice rather than the practice adapting to it.

More broadly, the same agentic approach (screenless, voice-first, nothing acted on without confirmation) isn't specific to craft.

Within the current system

  • 01An operational Agent page, so the dashboard becomes a real point of contact rather than a display.
  • 02Reminders tied to curing and firing times.
  • 03Deeper integration with the invoicing tools makers already use, rather than the project's own Sheets-based system.
13

Thesis book

Design Rationale.

A full design rationale documents every research phase, design decision and technical choice behind Lugh in depth.

Read the full Design Rationale ↗

The thesis book: a spiral-bound cork cover reading “Makers, not managers”
26 Makers, not managers.

[ In the end ]

Any trade where the work happens with the hands and the admin happens somewhere else carries the same burden, and could carry the same kind of agent.

← All work