Skip to content

Services

Four kinds of work. Each sheet below says what it covers, the order we build it in, the tools, and what is yours when we hand it over.

SYSsheet 1 of 4

Custom systems

Internal software that replaces spreadsheets, paper forms and the manual steps between them. It is built around how your team already works: who enters what, who approves it, and which reports come out the other end.

requestsrunswritesrecordssends01Peoplestaff, managers, finance02APIguard: roles03Approvalsdocuments, reports04MySQLthe records05Audit logwho did what06Notificationssent by the API

What it usually covers

  • Staff accounts with roles, so each person sees and changes only what their job needs
  • Approval flows with a record of who approved what, and when
  • Documents and PDFs generated from the data, not typed again
  • Reports and exports your accounts and management already use
  • Moving your existing records across from spreadsheets or an older system

Stack

Interface
Nuxt (Vue), Tailwind CSS
Server
Nest.js with Swagger API docs
Data
Prisma, MySQL

How we build it

  1. Map the work

    We sit with the people who do the work and write down every step, form and hand-off as it runs today.

  2. Agree the scope

    A written scope lists the screens, roles and rules. Nothing is built until you have agreed it.

  3. Build in stages

    Each stage goes up on a preview link your team can use with test data before the next stage starts.

  4. Move the data

    Existing records are imported and checked against the originals before the old process is switched off.

  5. Go live and support

    We release, watch the first weeks of real use, and keep making changes as the business changes.

What you get at handover

  • Source code in a repository you own
  • Developer documentation: how to run, configure and deploy it
  • The list of roles and what each one can do
  • Every database change written out as a script you can read
WEBsheet 2 of 4

Web apps and websites

Customer-facing web applications and company websites. Pages are rendered on the server, so they load quickly on a phone and search engines and link previews can read every one of them.

page requestreadsqueries01Browserphone, desktop02Server renderhtml, meta, json-ld03APIcontent and data04Databasebehind the API

What it usually covers

  • Customer accounts, sign-in and dashboards
  • Enquiry and booking forms that send to your mailbox, with spam protection
  • Content pages, case studies and product listings
  • Search titles, descriptions and share previews set for every page
  • Layouts checked on phones down to 320 pixels wide

Stack

Framework
Nuxt (Vue), server-rendered
Styling
Tailwind CSS
Hosting
Chosen per project, with a server where forms need one

How we build it

  1. Content and structure

    We agree the pages, what each one is for and the words on it before any design starts.

  2. Design

    One design system for the whole site, shown to you on a preview link rather than as static pictures.

  3. Build

    Pages are built on that system and tested for speed and accessibility as they are made.

  4. Launch

    We point your domain at it, set up redirects from old addresses, and submit the sitemap.

What you get at handover

  • Source code in a repository you own
  • A guide to updating content, where you will be doing it
  • Speed and accessibility results measured at launch
  • Access to the hosting account in your name
APPsheet 3 of 4

Mobile apps

iOS and Android apps built from one codebase and connected to a real backend. When a web system already exists, the app reads from the same API, so staff on the web and customers on their phones see the same data.

buildsrequestsrequestssends01One codebasereact native + expo02iOS, Androidthe installed apps03APIshared with the web04Web systemsame API05Pushnotifications

What it usually covers

  • Sign-in and accounts shared with your web system
  • Push notifications
  • Camera, location and file uploads where the work needs them
  • Builds for the App Store and Google Play

Stack

App
React Native, Expo
Builds
EAS Build for iOS and Android
Backend
The same Nest.js API as the web system

How we build it

  1. Agree the flows

    We list what a person does in the app, screen by screen, and which data each screen needs.

  2. Build the API first

    The backend the app talks to is built or extended first, so the app is never waiting on fake data.

  3. Build and test on devices

    Test builds go to your phones as each set of screens is finished.

  4. Store release

    We prepare the store listings and submit the builds for review.

What you get at handover

  • Source code in a repository you own
  • Store listings under your own developer accounts
  • Developer documentation for building and releasing new versions
DNSsheet 4 of 4

Domains and business email

Domain registration and email on your own domain, set up so that mail arrives and does not land in spam. We look after renewals and record changes, so the website and the mailboxes keep working.

registerspoints toAMXTXT01Registrarholds the registration02Your domainthe name people type03DNS zoneA, CNAME, MX, TXT04Websiteyour site05Mailboxesbusiness email06Spam checksspf, dkim, dmarc

What it usually covers

  • Registering a new domain or moving one you already have
  • Renewals tracked so the domain does not lapse
  • DNS records for the website, mail and any other services
  • Business mailboxes on your domain
  • SPF, DKIM and DMARC records, which mail providers check before accepting your mail

Stack

Records
A, CNAME, MX, TXT
Mail checks
SPF, DKIM, DMARC
Mail
Business mailboxes on your domain

How we build it

  1. Check what exists

    We list where the domain is registered today and every record it already has.

  2. Set up or move

    Records are created or moved over with the website and mail kept running throughout.

  3. Set up mailboxes

    Mailboxes are created and connected on the phones and computers your team uses.

  4. Look after it

    Renewals and record changes are handled when you need them.

What you get at handover

  • A written list of every DNS record and what it is for
  • Renewal dates in writing
  • Mailbox settings for each device

Not sure which sheet fits?

Most projects start as a problem, not a service. Describe what is slow, manual or missing and we will tell you which kind of work it is.