Web development · App development · Freelance

Websites. Apps.Follow the Built to workwhite rabbit. for you.Build what’s next.

Websites that win customers. Apps that simplify work. And an experienced developer who works directly with you.See past the surface. Turn the idea in your head into a website or app in the real world, with an experienced engineer beside you.

Fixed-budget websites and apps.
Freelance support at Pricing agreed together. UK-based, remote-first.

Your business, presented properly. Explore web development ↗

UK software consultancy · Outside IR35 Explore what we can build

Experience built
in good company.

BBC Studios, Nando's, Mastercard, TreeCard, and Thirdfort

Commercial experience across previous roles and engagements.

Built by PickTech. Shared with everyone.

Serious engineering.
Open to the community.

Two flagship projects that show how we think, design, and build. Explore the code, learn from the decisions, and use what helps you build something of your own.

Go library

Open source · MIT licence

Go Collections

Useful building blocks. Carefully engineered.

A type-safe Go library for everyday data problems: maps, sets, lists, queues, caches, and more. Generics and concurrent implementations help developers express their ideas clearly and handle shared data safely.

Add it to your project

go get github.com/pickeringtech/go-collections

CI, mutation testing, benchmarks, and runnable examples make the engineering open to inspection. Use the library, study the implementation, or contribute an improvement.

Programming language

Experimental · MIT licence

Fortis

AI-written code. Human understanding.

A statically checked, compiled language designed for software written by AI agents and reviewed by people. Ownership, changes, failures, and effects are explicit, giving reviewers concrete decisions to inspect in the source.

pure
Checked purity
try
Declared failure
let mut
Visible changes

An ambitious demonstration of language design, compiler engineering, and developer tooling. Explore annotated programs and guides for people and agents, or try the toolchain. Fortis is in active development, ahead of a stable 1.0 release.

Two ways to work together

Your priorities.
The right way to deliver.

Websites, apps, and practical engineering help. Choose the certainty of an agreed scope, or the flexibility of booking development time.

Fixed-budget projects

Your budget. An agreed scope.

Tell us what you need to achieve and what you can invest. We shape a deliverable that fits, then agree the scope and total before starting.

  • A written brief, clear deliverables, and acceptance criteria.
  • Payment milestones agreed up front.
  • A smaller first release or phased delivery when that makes more sense.
Explore fixed-budget delivery

Day-rate development

Pricing agreed together

Bring in experienced development support for your team, an evolving product, or a focused piece of work. Agree the time and priorities together.

  • Book a focused day or a longer engagement.
  • Review progress and adjust priorities as you learn.
  • Agree a spending limit and review point before extending the booking.
Explore day-rate support

Remote-first delivery. Outside IR35 engagements available. Scope, availability, and terms agreed before work begins.

Good work, for the public good.

Reduced rates are available for selected work that serves the public good. Tell us who your project helps, the impact you want to make, and your budget. Eligibility and any discount are agreed individually before work begins.

Ask about reduced rates ↗

Start with your priorities and a budget you are comfortable with. See an example brief and pricing options ↗

A process you can follow

Small steps.
Visible progress.

You know what is being built, why it matters, and what comes next. There is room to learn without letting the brief drift.

How we work together
  1. 01

    Plan

    Agree the finish line.

    We define the pages, features, dependencies, and what a successful delivery looks like. You get a written scope and clear commercials.

  2. 02

    Prove

    Resolve the unknowns.

    A design direction or focused prototype gives you something concrete to review before we commit to the full build.

  3. 03

    Build

    See it come together.

    Working previews and regular updates keep decisions close to the work. The important journeys are tested as we go.

  4. 04

    Improve

    Launch with a handover.

    Your code, access, and next steps are handed over clearly. Further improvements and ongoing support are agreed separately.

Richard Pickering, founder of Pickering Technologies

Richard Pickering

Your developer. Your direct point of contact.

A small business. Serious engineering.

Work with the person
doing the work.

From your first conversation to the final handover, you work directly with me. Senior judgement, honest communication, and care for the details that keep software useful.

The work is reviewable.

Public code, tests, and technical writing show how I approach dependable delivery.

The ownership is yours.

Clear handovers and documented decisions give you something you can keep building on.

Richard’s personal website (rpickz.io)

Your next move

Something in mind?
Let’s make it happen.
Ready to see how deep the rabbit hole goes?

Tell me what you need, what you have already, and when you would like to get started. We’ll work out the right scope together.

PickTech consoleOperator console

A different way to explore. Type help to begin.Connection established. Follow the white rabbit. Type help.

↑↓ history · Ctrl+R search · Tab complete