Skip to content
OutFinda
hello@outfinda.comStart a project

Software thatruns the business,not just the website.

Come to me before the problem is fully defined. Patient portals, CRMs, marketplaces and booking systems, from the first call to production.

Start a projectSee the work
Studio since
2022
Scope to launch
2–6 wks
On your own accounts
Day one
Lighthouse, every build
90+
  • Next.js
  • React
  • TypeScript
  • Node.js
  • NestJS
  • React Native
  • Supabase
  • PostgreSQL
  • Remix
  • Vue.js
  • Tailwind CSS
  • WebSocket

01What I build

Systems peoplerun a business on

Six kinds of system, and the problem each one exists to solve. Client work is covered by agreement, so I walk you through it on a call.

02Services

Four waysto work together

Each one starts with a written scope and ends with a codebase you own outright.

  1. Put something real in front of users before you hire a team

    For founders who need to test an idea with people rather than describe it in a deck.

    • One core workflow, built end to end with real data
    • Accounts, a basic admin view and a hosted URL you can share
    • Deployed on your own accounts from day one
    • A written note on what to build next and what to leave out
    • Next.js
    • Supabase
    • Auth and roles
    • Hosting setup
    • Scope note

  2. A complete application a team will rely on every day

    For businesses that need the system their operation actually runs on, customer-facing or internal.

    • Accounts, roles and permissions enforced in the database
    • Billing, integrations and background jobs as the scope requires
    • Tests on the paths where a failure costs money
    • Documentation, a deployment pipeline and a recorded handover
    • Next.js and Node
    • PostgreSQL
    • Payments
    • Background jobs
    • Automated tests
    • CI and deploys

  3. iOS and Android without building the same product twice

    For teams whose product needs to be on a phone, sharing a backend with what they already have.

    • One React Native and Expo codebase for both platforms
    • Shared API and data layer with your existing web product
    • Push notifications, offline handling and deep links where needed
    • Store submission handled, in your own developer accounts
    • React Native
    • Expo
    • Push notifications
    • Offline
    • Store release

  4. One person who already knows the codebase

    For teams with a live product and nobody on staff to look after it.

    • A fixed number of days each month for features and fixes
    • Dependency upgrades, monitoring and error triage
    • A written summary of what shipped at the end of every month
    • Priority response for incidents, at any hour
    • Retainer
    • Monitoring
    • Upgrades
    • Incident response
    • Monthly report

The goal is a working system

How this differs from an agency retainer or a contract developer.

The goal is a working system, not a delivery
The usual arrangementHow I work
Bills for hoursFixed scope, fixed price, fixed date
A team you never actually meetThe person writing the code
Design thrown over a wall to a build teamOne person from first call to production
The work lives in the agency's accountsEverything on your accounts from day one
Ends at the final invoiceEnds with a runbook and a walkthrough
The know-how leaves when they doDecisions written down and handed over
Uses AI to bill the same hours fasterUses AI to explore more before committing
Talk through which one fits

03Process

First callto handover

Hiring someone you have never worked with is a risk. Each step exists to keep that risk small, and to give you a way out if it is not working.

  1. Step 1: A thirty-minute call

    You describe the problem and what a good outcome looks like. I ask questions, say honestly whether this is a fit, and if it is not, point you somewhere better. There is no pitch deck.

  2. Step 2: A scope you can hold me to

    Within a few days you get a one-page plan: what is in, what is out, the milestones, a fixed price and a launch date. You pay nothing until you approve it, and the plan is the contract.

  3. Step 3: Working software every week

    Each week you see the real product running on a staging URL, not slides or mockups. If something is wrong you find out early, while changing it is still cheap.

  4. Step 4: Handover, not lock-in

    The code lives in your GitHub, on your hosting and your accounts, with documentation and a recorded walkthrough. You can bring in anyone else at any point, and leaving should be easy.

You own the system, not a rental

Everything below is yours at handover, in a form your next engineer can pick up without calling me.

Leaving should be easy. If it is not, you were never a client, you were a dependency.

  • The codebase, in your GitHub organisation
  • Infrastructure and databases on your own accounts
  • The written scope and the decision log behind it
  • Automated tests on the paths that matter
  • A deployment pipeline anyone can run
  • A recorded walkthrough of the whole system
  • A runbook for the failures you are most likely to hit
  • Environment variables and access, documented

04Studio

One person, and twoagents on the groundwork

Small on purpose. You talk to the person writing the code, decisions get made in a day, and nothing is lost in translation between a salesperson and a delivery team.

  • Syed Ahmad, founder and engineer at OutFinda

    Syed Ahmad

    Founder, engineer, designer

    Full-stack developer in Lahore, working with founders and teams worldwide. Takes a project from the first call to production: scope, architecture, interface, code, deployment and handover. Everything that ships has been through my hands.

  • Wren

    AI agent, research and groundwork

    Reads the domain before I do. Pulls apart competitors, standards and edge cases, and lays out the questions a scope has to answer. It gathers; the judgement about what matters stays with me.

  • Kiln

    AI agent, prototyping and first drafts

    Turns a decision into something runnable fast: a prototype to react to, a first pass at a migration, the repetitive checks nobody should do by hand. Everything it produces is reviewed and usually rewritten before you see it.

Wren and Kiln are AI agents, not employees. They widen what gets explored and shorten the distance to a first draft. Every decision, every review and everything that reaches you is mine, and I am accountable for it.

How one engineer ships like a team

Your decisions, my hands, and agents doing the groundwork. The loop is the product: every project sharpens the playbook the next one starts from.

AI widens what gets explored and how fast a draft appears. It never makes the call. Quality, context and anything touching a patient or a payment stays with a person, and that person is accountable for it.

  1. ScopeA plan you approve
  2. BuildWorking software weekly
  3. ShipInto production, on your accounts
  4. MeasureWhat worked, what did not

At the centre

Written-down know‑how

Decisions, patterns, runbooks

Anyone can produce software now. Knowing what to build is the job.

A model can write a thousand lines an hour.It cannot tell you which thousand your business needs.

I look for the process the software is really for,and design the system that carries it.

I don't hand over a design and call it finished,and I don't hand over code that nobody can run.

I stay until it ships, gets used,and holds up through the week that follows.

And when the work ends,the decisions and the runbook stay with you.

That is what a studio of one owes a client.

Let's build it

Tell me what you are trying to build or fix, in a few sentences. You will hear back from a person, not an autoresponder.

Email
hello@outfinda.com
Book a call
30 minutes, no pitch

You get a reply with a few questions, or a time for a thirty-minute call. Nothing is booked or billed until you say so.

Or email hello@outfinda.com