Skip to content
Taking new projects

I ship software weekly.You own every commit.

Custom apps, APIs and AI integrations for startups and small teams. One senior engineer, twelve years of production systems, a staging URL in week one.

45 minutes. You leave with a written scope either way.

6,424 commits across 91 repositories in the last twelve monthsHover a week for detail
years shipping
12+
projects delivered
40+
response, worst case
48h

  • TypeScript
  • Ruby on Rails
  • React
  • Next.js
  • Kotlin
  • PostgreSQL
  • Kafka
  • MongoDB
  • AWS
  • Terraform
  • Python
  • Docker

01Services

What I take on

Six things, narrow on purpose. If your problem is not one of them, I will say so on the first call instead of billing you to find out.

  • 01

    AI integration

    LLM features that survive contact with production: retrieval, evals, cost ceilings, graceful degradation when the model is wrong.

    • RAG pipelines
    • Evals and guardrails
    • Cost control
  • 02

    API engineering

    Versioned, documented, boring-on-purpose APIs. Contract-first, so the clients you have not built yet still work.

    • REST and GraphQL
    • OpenAPI contracts
    • Auth and rate limits
  • 03

    MVP and SaaS builds

    The smallest thing that proves the hypothesis, built so the second version is a refactor and not a rewrite.

    • Idea to launch
    • Billing and auth
    • Multi-tenant from day one
  • 04

    Backend architecture

    Event-driven systems, data modelling, and the unglamorous work of making a service you can debug at 3am.

    • Event pipelines
    • Observability
    • Migration strategy
  • 05

    Mobile and game builds

    Games and phone apps that reach both stores from one build, with the simulation underneath testable without a screen attached.

    • iOS and Android
    • Game loops
    • Offline-first
  • 06

    Technical audit

    An honest read on the codebase you inherited. What to fix, what to leave, and what the real cost of each is.

    • Codebase review
    • Risk register
    • Prioritised roadmap

02Process

How the work runs

Four steps, and you can walk away after any of them. The first costs you 45 minutes and leaves you with a written scope you own either way.

  1. 0145 min

    Scope call

    You describe the problem. I push back on the parts that do not need building yet. You leave with a written scope whether or not we work together.

  2. 022-4 days

    Shaped plan

    A concrete plan: architecture, milestones, fixed price or rate, and the risks I can see. No slides.

  3. 03Ongoing

    Weekly shipping

    Working software every week on a staging URL you can click. Progress is a deployment, not a status update.

  4. 04Final week

    Handover

    Documented, tested, and running in your infrastructure with your credentials. You can hire someone else to extend it, and that is the point.

03Selected work

Three systems, built end to end.

No logos and no screenshots. What a system does under load is the only interesting part, so that is what is on the page.

  • 01Payments data2026

    BIN lookup API

    Processes card BIN lookups through a two-tier cache, restricting paid upstream requests to a single call per BIN. Integrates a parallel, isolated IP-geolocation pipeline for graceful degradation.

    • TypeScript
    • MySQL
    • Redis

    2M+

    BIN records covered

  • 02Games, side project2026

    Loose Board

    Independent game label for mobile idle games. All titles share a centralized, headless simulation core to enable automated logic testing independent of the rendering engine.

    • TypeScript
    • Next.js

    10+

    iOS and Android projects

  • 03Lead generation2026

    Lead Engine

    Lead generation pipeline. Optimizes API consumption by deduplicating source polling across projects. Lead scoring utilizes an ordered, multi-model fallback architecture.

    • Next.js
    • BullMQ
    • Redis
    • Prisma

    < 1s

    lead processing

04Engagement

A retainer, or a fixed price for a fixed scope.

You always know the number before work starts. Retainers cancel with 30 days notice and unused hours roll over once.

  • Starter

    Up to 10 hours

    $950per month

    For founders who need a senior pair of hands on a specific thing.

    • Up to 10 hours per month
    • Async updates, shared board
    • Two-day response time
    • Rolls over one month
  • Studio

    Recommended

    Up to 30 hours

    $2,500per month

    For teams shipping continuously who want a reliable weekly cadence.

    • Up to 30 hours per month
    • Weekly call and staging deploys
    • Same-day response time
    • Architecture review included
    • Direct line, no ticket queue
  • Project

    Defined deliverable

    Fixedquoted per scope

    For a known deliverable with a deadline you actually care about.

    • Fixed scope, fixed price
    • Milestone billing
    • Written architecture plan
    • 30 days post-launch support

All prices exclude VAT. Invoiced monthly, net 14.

Questions

The things people ask on the first call.

05Contact

Tell me what is broken, or what should exist

One email starts it. No form, no discovery deck, no sales sequence.

hello@bitbybit.pl
+48 695 926 259

Local time in Wroclaw:


  • Reply time

    Within 48 hours at the very worst, usually the same working day. Put the deadline in the subject line if there is one.

  • First call

    45 minutes, no slides. You describe the problem, I argue with the parts that do not need building yet. You leave with a written scope either way.

  • Right now

    Taking new projects. One slot open for Q4.