// farman-labs / services

Pick your problem.We'll build the fix.

Start with whatever costs your team the most time. Each system works on its own and connects to the others when you're ready.

// farman-labs / services / portals

Client & Supplier Portals

Customers keep calling to ask where their order is?

Customers order and track online. Your team stops re-typing.

Sound familiar?

  • Orders arrive by email, phone and WhatsApp, and get re-keyed by hand, with errors.
  • Print files and job specs come in the wrong format or resolution, and are found late.
  • Customers call to ask “where is my order?” several times a day.
portals.farmanlabs.app
Illustration of a portals screen. A branded, secure web portal where customers place and track orders and suppliers confirm and update them, so your team stops re-typing emails into spreadsheets.

How it flows

  1. 01

    Guided form

    Customer orders

  2. 02

    Size · bleed · CMYK · dpi

    File preflight

  3. 03

    Written once

    Job record

  4. 04

    Email + SMS each step

    Live status

What we build

  • Order intake

    Guided forms with product-specific fields, quantity breaks, due dates and repeat-order shortcuts.

  • File upload and preflight

    Drag-and-drop upload of print-ready PDFs, checked for page size, bleed, colour mode and resolution, with a clear pass or fail message.

  • Custom job specs

    A spec builder per product (stock, finish, binding, dimensions) that feeds the production job record.

  • Status tracking

    A live order timeline driven by the same data the shop floor updates.

  • Automated notifications

    Email and SMS at each status change, proof-approval links and delivery confirmation, with no staff action needed.

  • Supplier side and accounts

    Purchase orders pushed to suppliers. Company accounts with roles, row-level security and SSO-ready sign-in.

What changes for you · targets

Staff time on order entry

Cut by 60–80%

Orders with missing or wrong specs

Cut by over half

“Where is my order?” calls

Cut by over half

Order to production-ready

Same day

Targets we measure against your baseline in every engagement, not past results.

Where it sits in the system
  1. Customers, suppliers, email
  2. Portals
  3. Pipelines
  4. Shared database
  5. Dashboards
Book a call about portals

// farman-labs / services / automation

Workflow Automation Pipelines

Still typing supplier invoices into QuickBooks?

Invoices and emails become data automatically.

Sound familiar?

  • Staff spend hours a week keying supplier invoices, POs and delivery notes into QuickBooks or the ERP.
  • Data lives in several tools that disagree: the spreadsheet says one thing, the accounting system another.
  • Routine steps (send the invoice, chase the approval, update the stock count) depend on someone remembering.
automation.farmanlabs.app
Illustration of a automation screen. Background systems that read the documents and emails your business already receives, pull out the data and put it where it belongs, with no copy-paste.

How it flows

  1. 01

    Dedicated inbox

    Email or PDF arrives

  2. 02

    Fields + confidence

    Parser reads it

  3. 03

    Below 90% only

    Review if unsure

  4. 04

    QuickBooks / ERP

    Posted to the books

What we build

  • PDF and invoice parsing

    Extracts vendor, line items, totals, tax and PO numbers. Low-confidence fields go to a review queue, not straight into the books.

  • Email parsing

    A dedicated inbox whose messages and attachments become structured records automatically.

  • Database syncing

    Two-way sync between your database and your spreadsheets or line-of-business tools, with conflict rules.

  • QuickBooks and ERP bridges

    Creates bills, invoices, customers and items through official APIs, with matching to avoid duplicates.

  • Background jobs

    Scheduled and event-driven jobs with retries, step-level logs and alerts on failure.

  • Review and audit trail

    An approval screen for exceptions, and every automated action logged with its source document.

What changes for you · targets

Manual data entry

10–30 hours a week saved

Data-entry error rate

Under 1% after review

Invoice to books

Minutes, not days

Month-end close

Days saved

Targets we measure against your baseline in every engagement, not past results.

Where it sits in the system
  1. Customers, suppliers, email
  2. Portals
  3. Pipelines
  4. Shared database
  5. Dashboards
Book a call about automation

// farman-labs / services / dashboards

Real-Time ERP & Operations Dashboards

Walking the floor to find out what's late?

Every job, crew and asset on one live screen.

Sound familiar?

  • The owner has to walk the floor or call around to know where things stand.
  • Job status lives on whiteboards and in people's heads, so handovers drop work.
  • Field crews get dispatched by phone and text, with no record of who went where.
dashboards.farmanlabs.app
Illustration of a dashboards screen. One live screen showing every job, crew and asset, updated the moment something changes, built around how your business actually runs instead of a generic ERP's idea of it.

How it flows

  1. 01

    Drag a card · scan

    Floor updates a job

  2. 02

    Shared database

    Saved once

  3. 03

    No refresh

    Every screen updates

  4. 04

    Late job · low stock

    Alerts fire

What we build

  • Kanban job boards

    Drag-and-drop boards per department, with due-date warnings and capacity limits.

  • Field dispatch

    Assign jobs to crews on a calendar and map. Crews check in, add photos and notes, and capture signatures.

  • Inventory and assets

    Stock levels with reorder points, barcode or QR scanning from a phone, and equipment history.

  • Real-time updates

    Changes reach every open screen instantly, with no refresh and no stale data.

  • KPI dashboards

    Throughput, on-time rate, backlog, revenue by customer and crew utilisation.

  • Alerts

    Rules such as “job late by 1 day” or “stock below reorder point” trigger email, SMS or Slack messages.

What changes for you · targets

Owner's status picture

Seconds, any device

On-time delivery rate

Up vs. baseline

Status meetings and calls

Cut by over half

Stockouts and lost equipment

Cut by over half

Targets we measure against your baseline in every engagement, not past results.

Where it sits in the system
  1. Customers, suppliers, email
  2. Portals
  3. Pipelines
  4. Shared database
  5. Dashboards
Book a call about dashboards

// farman-labs / services / custom

Custom Software Development

Software that only does 80% of the job?

The system your operation needs, when no product fits.

Sound familiar?

  • Off-the-shelf software covers 80% of the job, and staff work around the other 20% with spreadsheets.
  • A core process (quoting, scheduling, costing) lives in one person's head or one fragile spreadsheet.
  • Several disconnected tools each hold part of the picture.
custom.farmanlabs.app
Illustration of a custom software screen. Full-stack software engineered around one operation's unusual work: quoting engines, scheduling tools, scanners and internal apps that no off-the-shelf product handles.

How it flows

  1. 01

    Scope + fixed quote

    Blueprint

  2. 02

    On staging

    Weekly demos

  3. 03

    Before go-live

    Tests and runbook

  4. 04

    Code + data yours

    Your repository

What we build

  • Web and mobile apps

    Internal tools, customer apps and shop-floor screens on Next.js, built for phones, tablets and desktops.

  • Quoting and costing engines

    Your pricing rules, materials and labour turned into instant, consistent quotes.

  • Scheduling and capacity

    Planning tools that know your machines, crews and lead times.

  • Integrations and APIs

    Connections to accounting, ERPs, carriers, payment providers and machinery through official APIs.

  • Data model and security

    A Supabase Postgres schema with row-level security, backups and audit logs.

  • Tests and documentation

    Automated tests, a written runbook and the code in your repository from day one.

What changes for you · targets

Quote

Fixed by the Blueprint

First release

2–3 weeks

Code and data

Yours, in your repo

Handover

Documented

Targets we measure against your baseline in every engagement, not past results.

Where it sits in the system
  1. Customers, suppliers, email
  2. Portals
  3. Pipelines
  4. Shared database
  5. Dashboards
Book a call about custom software

// farman-labs / services / system

How itconnects.

Hover or tab through a part to see what it talks to.

writeswritessynclive readsCustomersPlace and track ordersSuppliersConfirm, upload docsEmail and PDFsInbound orders, invoicesClient & Supplier PortalsSign in, submit, approve and trackAutomation PipelinesRead, check and routeSupabase Postgres + StorageOne source of truth for orders, documents, statusesQuickBooks / ERPBridged both waysReal-Time DashboardsLive orders, throughput and exceptionsStaff and ownerAct on what they see

// farman-labs / services / pricing

Priced inthree steps.

Each step is scoped and priced on its own, so you can stop after any step with something useful in hand.

01 · Paid Blueprint

Price (USD)
$500–$1,000
Duration
1–2 weeks
What you get
  • Workflow map of the current process
  • System architecture and data model
  • Screen list
  • Fixed quote and timeline for the build
Exit point
You own the blueprint and can build with anyone.

02 · Fixed-Scope Build

Price (USD)
$5,000–$10,000+
Duration
2–3 weeks for a first release
What you get
  • The working system, deployed
  • Data migrated
  • Staff trained
  • Documentation and admin access
Exit point
Code and data belong to you.

03 · Monthly Retainer

Price (USD)
$1,000–$1,500 / month
Duration
Ongoing, cancel with 30 days' notice
What you get
  • Hosting and monitoring
  • Bug fixes
  • Small changes (hours set per plan)
  • Monthly usage and outcome report
Exit point
Full handover package on exit.
  • The Blueprint fee is credited against the Build if you proceed within 60 days.
  • The Build quote is fixed by the Blueprint. A change outside scope becomes a written change order before work starts.
  • Every Build ships to production in 2–3 weeks. Larger systems ship in phases, each with its own fixed scope.

// farman-labs / next-step

Tell us whereit hurts.

Where does work get re-typed, chased or lost? In 30 minutes we’ll show you what the fix looks like and roughly what it costs.

Start with a Blueprint

You talk to the person who would build it. No sales team, no obligation.