Niko M.web + software engineer
Internal tools / operationsWorking food-operations and household-finance apps

Replace the spreadsheet maze with one working workflow.

I turn the decisions a small team makes every day into a private application: what came in, what changed, who did it, what it cost, what needs attention, and how to recover.

FIFO inventory and order margin · exact money ledger and linked transfers · multilingual mobile workflows

Delivery
Built for your operation
Infrastructure
Your server or cloud account
Typical scope
$15k–$70k+
Support
Handoff or ongoing help
The workflow

How the work moves

  1. Existing records
  2. One source of truth
  3. Daily work
  4. Reports and alerts
  5. Backup and export
What works now

The core workflow already works.

A private web application fitted to your records, rules, roles, daily actions, reports, imports, exports, and handoff requirements.

  • One primary team and workflow
  • Core records, states, and business rules
  • Mobile and desktop staff interface
  • Basic roles and access boundaries
  • Essential reports, imports, and exports
  • Deployment, backup, recovery, and handoff runbook
What I tailor

I fit it to how your team works.

I fit the data model, rules, interface, integrations, permissions, hosting, review steps, and reporting to your business. The real work is joining those parts without breaking the operation you already have.

Runs on infrastructure and provider accounts you control. Your operational policy, record retention, staff access, and regulated obligations remain yours.

What I can show

The current system already does this.

The existing work includes a bilingual food-operations PWA with purchases, FIFO stock, recipes, channel fees, orders, estimated margin, workspaces, plans, and exports; plus a private household-finance PWA with integer money arithmetic, linked transfers, budgets, debts, and imports.

Not a fit if

When I would not recommend it.

  • A process nobody owns or can explain
  • A generic ERP replacement at small-tool budget
  • Regulated accounting, banking, medical, or legal claims without the required specialist review
Related builds

These cases show the migrations, tests, and applications behind this system.

Food stock, recipes, and order marginA bilingual mobile workflow prepared for a controlled pilot. Private household financeExact ledger arithmetic, transfers, budgets, debts, and imports. This site’s durable contact intakeA small example of bounded public rendering and recoverable private state.
Before the full build

Start with a short technical planning phase.

$2.5k–$6k · usually 5–7 business days

I inspect the current system, map what can be reused, identify the risky parts, and leave you with a build plan and a tighter price. Clear scopes go straight to a quote.

Estimate your version

See which decisions move the price.

This gives you the right order of magnitude. Data quality, integrations, migrations, deadlines, and who runs production can move it.

Add what your version needs
Likely implementation range $15k–$70k+

The estimate assumes one main decision-maker, workable source data, your hosting, and that I keep the reusable core.

After launch
Send me this scope
After the build

Take the handoff or keep me involved.

For 30 days after handoff, I fix anything that does not match the agreed build. After that, you can run it yourself or keep me on for maintenance, production help, or reserved development time.

Handoff

No ongoing fee

You take over the agreed release. I still fix build defects for 30 days; ongoing updates and operational help are separate.

Maintenance

$1.5k–$3k/month

Annual commitment. Scheduled releases, security and compatibility fixes, and planned upgrade help. No incident response or custom development.

Production support

$3.5k–$6.5k/month

Six-month minimum. Maintenance, one-business-day response on working days, deployment help, and a monthly allowance for incident or operational work.

Reserved engineering

$7.5k–$12k/month

Six-month minimum. Priority queue, planned release work, and reserved engineering capacity. Unused capacity does not roll over; larger features are scoped separately.

The accepted workflow includes 30 days for defects against the agreed acceptance criteria. Process changes, new reports, ongoing operations, and incidents are separate work.