Skip to main content

File 03 / Services

Six kinds of work, filed plainly.

From shaping a product to keeping a finished site running. Each entry says what you bring and what ships, because a service list nobody can price is just decoration.

Ref 01

Product strategy and UX

You bring an idea, or a problem that keeps coming back. We work out what the product actually needs to be: who it serves, what it must do first, and what can wait.

Everything is marked out before anyone cuts, so the build starts from decisions already made.

What ships

  • A product definition with priorities you agreed to
  • User journeys and information architecture
  • Prototypes and a delivery plan you keep either way
Ref 02

Full-stack product development

You bring the plan, ours or your own. We build the working thing: Next.js and React up front, authentication, databases and integrations behind it, deployed and running at a real URL.

SENVault came out of this studio and we run it every day, so we build like the person on call is us. It usually is.

What ships

  • A working web application you can put in front of users
  • Auth, database and integrations wired in
  • Deployment, with a staging link from the first week
Ref 03

Websites for growing businesses

You bring a working business and a site that undersells it. We write the positioning with you, design something with your trade's own character rather than a template, and build the enquiry journey so the right people get in touch.

JG Technical's site is this service, live and checkable.

What ships

  • Positioning and page structure in plain words
  • A custom design and build, no theme underneath
  • SEO basics and a clear enquiry journey
Ref 04

Accessible digital design

You bring a product or site that some of your users find hard to use. We audit it properly, show you exactly what is blocking people, then fix it: structure, contrast, keyboard access, and calmer patterns for sensory-sensitive users.

This is the standard our own products are held to, so we are not reading the guidelines for the first time on your job.

What ships

  • An accessibility audit written in plain language
  • Inclusive interaction and content patterns
  • Hands-on remediation of what the audit finds
Ref 05

Workflow and information systems

You bring the spreadsheet nobody trusts and the shared drive nobody can find anything in. We map how the work really moves, then build the internal tool or secure portal that holds it straight.

Documents organised, information where the people who need it can reach it, and less of the same thing typed twice.

What ships

  • Workflow mapping and simplification
  • Document and information organisation
  • Internal tools and secure portals
Ref 06

Technical improvement and support

You bring something already built that creaks: slow pages, flaky deploys, a codebase nobody wants to touch. We audit it, fix performance and reliability first, and stay on hand afterwards.

Support from a small studio means the person who did the work answers, not a ticket queue.

What ships

  • A technical audit that says what to fix first
  • Performance and reliability fixes
  • Ongoing improvement with a direct line
Note

How a job starts

Whichever of these you need, the job runs the same four stages we keep on the home page: a first conversation, a plan on paper, a build in the open, then keeping it running. No stage is skipped because a job looks small.

The first conversation costs nothing and commits you to nothing. Describe the job as it stands, half-built or barely started, and you will hear plainly whether we are the right studio for it.