Skip to content
01The floor 02Cost check 03The line 04Lab notebook 05The crew 06Vote on what is next 07Questions 08Send a problem
Field manual — edition 01

We build tools that solve real problems.

Softwayer is a software factory. Every product gets its own subdomain, its own database, its own billing — and two weeks to prove itself. Problem → prototype → ship → scale or kill. Nothing else ships. * Real means it costs money, burns hours, or breaks every week. If it doesn't, we don't build it.

softwayer — factory --status
$ factory --list --live
    6 units on the line cycle time avg 11.4d

    01 — The floor · six units on the line#

    to browse

    02 — Cost check · rule 01 in a box#

    Nothing is sent anywhere

    Put a number
    on the annoyance.

    Rule 01: if a problem doesn't cost more than $500 a month, we don't build for it. Move the sliders and find out where yours lands.

    Annual cost of doing nothing

    $0

    Below the line

    Under $500 a month. Honestly? Keep doing it by hand — a tool would cost you more than the problem.

    03 — The line · how a unit gets built

    Four stations.
    Fourteen days.
    No decks.

    Every product runs the same rail. Fail a station and it gets logged and killed. We keep the code, we drop the plans.

    Cycle time avg · 11.4 days
    01

    Intake — the problem

    It has to cost real money, happen again next month, and be solvable in under 800 lines. Example on file: “$2,000 a month to send 40,000 emails.” That qualifies.

    STATION-01 · REV 03

    02

    Build — fourteen days

    Days 1–2 research. Days 3–9 build. Days 10–12 we use it ourselves on real work. Days 13–14 ship the subdomain and turn on billing. Miss the date and it goes to the kill log.

    STATION-02 · REV 03

    03

    Ship — its own subdomain

    One tool, one subdomain, one database, one billing account. No shared monolith. If a product dies it dies alone and nothing else notices.

    STATION-03 · REV 03

    04

    Scale or kill

    Thirty days to reach 100 people who actually use it. If it doesn't, we archive the marketing, keep the source, and write down what we got wrong. Blunt, but it keeps the floor clear.

    STATION-04 · REV 03

    04 — Lab notebook · Q1 2026#

    Page 14 / 42

    House rules

    How we find,
    and kill, ideas

    01 — Under $500 a month? Ignore it. 02 — Fourteen days, or it dies. 03 — One subdomain, one job. 04 — We use it before anyone pays for it.
    Pinned to the wall

    43 ideas in the backlog. Six percent of them will ever ship.

    Jan 04 — 09:14

    Problem hunt

    Cold email platforms bill per contact. We sent 12,000 messages last month and paid $840 for the privilege. Wrote down: self-hosted sending, inbox rotation, flat price. Killed the per-contact pricing model in the spec on the first pass.

    Logged

    Jan 11 — 22:03

    Rapid prototype

    Scraper running on a proxy pool, 0.4 seconds a lead in testing. Ran a thousand records through it to check the shape of the data. Cost per lead came out roughly forty times cheaper than the API we were quoting against. Moved it to station 02.

    In build

    Jan 19 — 16:41

    Scale or kill

    Vault holds 1.2 million keys in the load test, 11ms at p99. That one stays. Rankpulse is another story — nobody on the test list opened it twice. If it doesn't move by the end of February it goes in the log and we move on.

    Under review
    Experiments run 0 On the line 0 Killed 0 In the backlog 0

    05 — The crew · two people, no layers#

    Islamabad · async
    Badge 001On the floor

    Hassan Saleemi

    Co-founder & CEO

    Decides what goes on the line and what gets killed. Reads every problem submitted through this page and writes the reply himself.

    Badge 002On the floor

    Rizwan Ahmed

    Co-founder & CTO

    Owns the build. Writes the code that ships each tool to its own subdomain — and the code that takes it back down when a unit fails a station.

    06 — Next off the line · you pick#

    Your votes stay on this device
    Spec written34 votes

    Ghostwriter

    Turns a recorded walkthrough into a written procedure your team will actually follow.

    Researching27 votes

    Invoiceroid

    Payment received to a compliant invoice, emailed, in three clicks. Aimed at freelancers billing across borders.

    Idea19 votes

    Calibre API

    Generate PDFs and ebooks at volume through an API instead of babysitting a headless browser.

    Manifesto — v1.0

    We don't build startups. We build scalpels .

    One problem, one subdomain, built until it is genuinely good at that one thing. No dashboards about dashboards. If it doesn't remove a bill you're already paying or hand back five hours a week, it doesn't leave the floor.

    Bootstrapped No bloat No meetings Cancel any time

    07 — Questions we actually get#

    Straight answers
    01What does it cost?
    Products are a flat monthly price — no per-seat, no per-contact, no credits. Custom builds get quoted once after intake: a fixed number for a fixed scope, agreed before anyone writes code. No hourly billing and no retainers.
    02You kill products. What happens if I'm using one?
    Killing means we stop marketing it, not that we switch it off. If you're already using a tool you get thirty days notice, a full export of your data in a format you can actually open, and the tool stays up until you've moved. We'd rather lose the product than lose your trust.
    03Why does every tool live on its own subdomain?
    Each one has its own database, its own billing and its own deploy. Nothing is shared. An outage in one tool can't reach another, and you're never paying for a suite when you only need one thing.
    04Do you take on custom builds?
    Yes — that's what the form at the bottom of this page is for. Describe the problem and what it currently costs you. If it clears our threshold we reply with what we'd build and what it would take. If it doesn't, we say so and tell you why.
    05How quickly do you reply?
    Within twenty four hours. One person reads every intake and one person replies. There's no sales call, no discovery deck and nobody will add you to a mailing list.
    06Where are you, and how do we work together?
    Islamabad, Pakistan. We work asynchronously with people in any timezone — email and shared documents rather than scheduled calls. You'll get written updates at each station, not status meetings.

    08 — Intake

    Tell us what
    keeps costing
    you money.

    Describe the thing you keep paying for, or keep doing by hand. If it clears rule 01 we'll write back with what we'd build and what it would take. If it doesn't, we'll tell you that too — usually faster.

    Reply within 24h No sales call

    Factory intake — form 01

    0 / 600

    Related to a unit? (optional)

    No newsletter, no tracking pixels, no drip sequence. One human reads it and one human replies.

    On the floor

    Logged as . If it clears rule 01 you'll hear back inside 24 hours.