Custom software development

Software built by people who run their own.

We design, build, and operate production applications—our own and our clients'. That covers architecture, interface, data, testing, deployment, and the unglamorous work after launch.

The problem

Our products are the portfolio.

WindOp is a native Windows AI operator built with Tauri and Rust. Just Curves is a production dating platform with mutual-only messaging, encrypted conversations, photo verification, and human moderation. We build and operate both.

That matters for client work. We have already dealt with releases and auto-updates, stale caches, account security, moderation queues, email delivery, backups, and data recovery—the problems that appear after a demo becomes a product.

Every engagement starts with scope: who uses it, what it must do on day one, what can wait, and what it costs to run. You see the plan and the price before we write production code.

What's included

Everything it takes to ship it properly.

Each engagement is scoped to what you actually need. These are the pieces we cover.

Discovery and scope

  • User flows and must-have features
  • Technical plan, milestones, and a fixed quote
  • Running-cost estimates for hosting and services

Web applications

  • Next.js and TypeScript front to back
  • PostgreSQL data models, authentication, and roles
  • Payments, email, and third-party API integrations

Desktop applications

  • Windows apps with Tauri and Rust, or Electron
  • Installers and in-app updates
  • Native file, shell, and system integration

Quality and operations

  • Automated tests and accessibility checks
  • Deployment, monitoring, and backups
  • Documentation and a clean handoff
Who it's for

A good fit when…

Not sure which of these you are? Send the rough version and we will tell you honestly.

01 · First product

Founders and new ventures

You have a validated idea and need a first version that real users can rely on—and that can grow without a rewrite.

02 · Internal tools

Replacing spreadsheets and manual steps

Your team runs on copy-paste and shared spreadsheets. A focused internal app can remove the error-prone parts.

03 · Rescue

Existing apps that need help

An unfinished or unstable codebase. We audit first, then repair, refactor, or rebuild—whichever is the responsible path.

How it works

Clarity before code.

No mystery package and no disappearing after launch. You see the scope and the price before we build.

01 · Understand

Define the real job

Users, current pain, constraints, timing, and what success needs to look like.

02 · Scope

Make the work visible

A clear proposal with deliverables, boundaries, milestones, and price.

03 · Build

Ship in checkpoints

Working increments you can review, with testing at every step.

04 · Run

Launch with a handoff

Deployment, verification, documentation, and an option for ongoing care.

Questions

Straight answers.

Anything else? Ask in your first message and we will answer it directly.

We pick the stack that fits the job and your team. On the web that is usually TypeScript, Next.js, and PostgreSQL. On the Windows desktop it is usually Tauri with Rust. If you already have a stack, we can work inside it.

Yes. We start with a code and infrastructure review, tell you plainly what we found, and propose the smallest responsible next step before any rebuild is on the table.

Against a defined scope—fixed price per milestone where possible, so you know the cost of each stage before it starts. Ongoing work can move to a monthly arrangement.

Ownership terms go in the agreement before work begins, and source, deployment access, and documentation are part of the handoff.

Next step

Bring us the product you keep describing.

Tell us who it is for, what it has to do first, and where it is stuck today.