Source Softwares
Available for new projects · Q3 2026

Software for the work your team is still doing by hand.

I build internal tools, automations, dashboards, and file-processing systems for teams that have outgrown spreadsheets, email chains, and copy-paste work.

Solo contract engineer · Backend, full-stack, AI workflows · Based remote

workflows/vendor-intake.ts
// Before: 14 steps across 4 tools
// After:  1 endpoint, 1 dashboard

export async function onVendorPacket(file) {
  const doc      = await extract(file);
  const summary  = await ai.summarize(doc);
  const flags    = validate(doc, rules);

  await db.intake.insert({
    vendor:    doc.fields.vendor,
    needs_w9:  flags.includes("missing_w9"),
    status:    flags.length ? "review" : "ready",
    summary,
  });

  return notify.ops("New vendor packet ready");
}
$ npm run intake✓ deployed
The problem

The team isn't disorganized. The tools just don't match the work.

Most operations-heavy businesses run important work through spreadsheets, email threads, PDFs, shared drives, manual review, and a stack of disconnected SaaS tools. Each one solves a slice of the problem. The gaps in between are where the hours disappear.

Files spread across too many places

Drive, email, Dropbox, someone's desktop. Nobody is sure where the latest version lives.

The same review, every week

A person opens the file, checks the same fields, copies the result somewhere else. Repeat.

Copy-paste between systems

A row in one SaaS tool has to become a row in another. Nobody automated it, so a human does.

Spreadsheets running operations

A 14-tab workbook is somehow the source of truth, and only one person fully understands it.

Tools that almost work

The SaaS covers 80%. The remaining 20% is filled in with manual steps that quietly cost hours.

+ probably whatever you just thought of
What I build

Practical software, described in business terms.

Every project is scoped around the outcome you actually want — not the tech stack underneath. The stack is my problem.

Internal tools & dashboards

Custom dashboards and review queues so your team can track work, assign tasks, and see what actually needs attention today.

Admin panelsReview queuesReporting views

Document & file workflows

Upload, extract, validate, route. Turn the folder full of PDFs and spreadsheets into a structured pipeline your team can trust.

OCR + parsingData extractionApproval flows

AI-assisted workflows

Use models where they actually help: summarising, classifying, drafting, flagging. With a human in the loop and guardrails, not magic.

SummariesClassificationDrafting & review

API integrations

Get your CRM, billing, support, and ops tools to actually talk to each other. No more nightly CSV exports.

CRM ↔ opsWebhooksSync jobs

Backend & job processing

Reliable APIs, queues, and scheduled jobs that quietly run the parts of the business that nobody should be doing by hand.

APIsBackground jobsData pipelines

MVPs & prototypes

A first usable version of a product idea or internal tool, shipped fast enough to get real feedback instead of more meetings.

Prototypesv1 productsInternal pilots

Interactive demo

Document Intake + Review Queue

Upload documents, extract the important details, flag what needs review, and send clean results to your team.

Intake workspace

This demo does not upload or store your files. Use the example files below to preview the workflow.

Frontend-only simulation

Select at least one example file to run the demo.

What this demo is showing

This is not meant to be a real document processor. It is a frontend demo of the kind of workflow I can build for a client: secure intake, background processing, structured extraction, human review, and handoff into the tools the team already uses.

File intake

Give teams a clear place to collect messy documents without losing context.

Structured extraction

Turn scattered document details into fields people can compare and act on.

Human review queue

Route exceptions to the right person before work moves downstream.

About

Source Softwares.

Software engineer · Solo contractor · Source Softwares

I'm a software engineer who builds practical systems across backend, frontend, cloud, data, and AI workflows. I'm most useful on projects where the hard part is understanding the workflow and turning it into software that people can actually use.

Working with a solo engineer means one person scopes the work, builds it, and ships it — no account managers in between, and no two-week handoff for a two-hour change.

Areas I work across

Backend systemsFull-stack appsFile processingData pipelinesAI workflow featuresCloud deploymentInternal tools
Where this fits

If any of these sound familiar, we should talk.

Document-heavy operations

Leases, invoices, vendor packets, applications — anything that arrives as a PDF and gets reviewed by a human.

Spreadsheet-driven workflows

An Excel or Google Sheet has quietly become an operational database. It works, until it doesn't.

Manual handoffs between tools

Data leaves one SaaS as a CSV and gets pasted into another. A small integration would save hours a week.

Customer or vendor intake

Onboarding new clients, vendors, or partners involves the same checklist of fields, files, and approvals every time.

Internal review & approval queues

Multiple people approve things in email threads. Nobody knows what's pending without asking around.

How it works

Hiring me is meant to feel low-risk.

Small first commitments, working software early, and a clear way to decide whether to keep going. No retainers, no surprise scope.

  1. 01

    Map the workflow

    A short, focused conversation about how the work actually happens today — who touches what, where it breaks, and what the tools are getting wrong.

  2. 02

    Build a small version

    A prototype or first usable version, shipped quickly. Just enough product to see whether the idea holds up against real work.

  3. 03

    Turn it into a real tool

    Database, APIs, permissions, background jobs, integrations, deployment, reliability — added where they earn their keep, not by default.

  4. 04

    Improve from real usage

    Iterate based on what your team actually uses. Cut what they don't. Add what's missing once it's obvious.

Contact

Tell me about the workflow.

A few sentences is enough. I'll reply within a day with either a question, a rough direction, or a time to talk through it.

Protected contact form

The inbox address is not published publicly. Use the form and the request will route to the right email destination on the backend.

Replies within 1 business day · Remote, working across US & EU time zones

Spam protection

This form uses a bot check and server-side rate limiting.

Have a process your team keeps doing manually?

Send me what the workflow looks like today. I'll help figure out whether it should be a small tool, an automation, or something simpler — and what it would actually take to build.