Independent software studio

Senior engineering,
none of the overhead.

Technull is a deliberately one-person practice. When you hire Technull, you work directly with the engineer who designs, builds and ships your software — no account managers, no hand-offs, no junior bench learning on your budget.

Start a conversation → What I build
~/technull 
$ technull --about
model        independent practice
engineers    1 # by design
hand-offs    0
focus        backend · mobile · cloud
you talk to  the person writing the code
you own      100% of code & infrastructure

$ technull --status
✓ taking on a limited number of projects
$
Why a solo practice

Small on purpose. Accountable by default.

Most software projects don't fail on technology — they fail in the gaps between people. A single, senior point of ownership removes those gaps. Decisions are faster, context is never lost, and the quality bar doesn't depend on who got staffed this week.

01 / Direct

One point of contact

The person you brief is the person who architects, writes and deploys the work. Nothing is lost in translation.

02 / Senior

Experience on every line

No layers of delegation. Every technical decision is made with full context and long-term maintainability in mind.

03 / Focused

Few clients, full attention

I take on a limited number of engagements at a time, so your project gets real focus — not a slice of a sprint.

Services

From first commit to production.

End-to-end engineering across the stack, with an emphasis on systems that are simple to run, easy to change and built to last.

  1. /01

    Backend Systems

    APIs, services and data layers designed for scale, security and clarity. Sensible architecture over fashionable complexity — software your future team will thank you for.

    • API design
    • Distributed systems
    • Databases
    • Performance
  2. /02

    Mobile Applications

    Fast, intuitive apps for iOS and Android — from product idea to App Store and Play Store release, with the backend to match.

    • iOS
    • Android
    • Cross-platform
    • Store release
  3. /03

    Cloud & Infrastructure

    Reliable, observable, cost-aware infrastructure. Automated deployments, infrastructure as code and monitoring that tells you about problems before your users do.

    • Infrastructure as code
    • CI/CD
    • Observability
    • Cost optimisation
  4. /04

    Technical Consulting

    An experienced second opinion when it matters: architecture reviews, technology choices, code audits and hands-on guidance for founders and in-house teams.

    • Architecture review
    • Code audits
    • Fractional CTO
    • Roadmapping
Process

Clear steps. No surprises.

A lightweight process built around transparency: you always know what's being built, why, and what comes next.

  1. Discover

    A focused conversation about your goals, constraints and what success looks like. Honest advice — including when not to build.

  2. Plan

    A written proposal with scope, architecture, milestones and cost. Clear enough to make a decision on.

  3. Build

    Iterative delivery with regular demos and working software early. You see progress, not status reports.

  4. Hand over

    Clean code, documentation and deployment in your own accounts. Ongoing support available if you want it.

Ways to work together

Flexible engagements.

Every project is different. Choose the model that fits your stage — we'll agree on scope and terms before any work begins.

FAQ

Good questions.

Working with an independent engineer is different from hiring an agency. Here's what clients usually ask first.

Why work with a solo engineer instead of an agency?

You get senior expertise on every part of your project, direct communication, and lower overhead. Agencies often sell senior talent and staff junior engineers; with Technull, the expert you talk to is the one doing the work.

What if you become unavailable?

Continuity is built into how I work. Everything lives in your own repositories and cloud accounts, code is written to be read by others, and every project ships with documentation for setup, deployment and architecture — so any competent engineer can pick it up.

Can a single person handle my project?

For many projects, yes — and often faster than a larger team, because there's no coordination overhead. If your project genuinely needs more people, I'll tell you upfront during discovery rather than overpromise.

Who owns the code?

You do. All source code, infrastructure and intellectual property created for your project belong to you, and are delivered in accounts you control.

How do we get started?

Send a short email describing what you're working on. I'll reply to set up an introductory call, and if it's a good fit you'll receive a written proposal with scope, timeline and pricing.

Contact

Let's build something solid.

Tell me about your product, your timeline and what's getting in the way. You'll hear back personally — usually within one business day.

Remote, worldwide Direct reply, no sales team