nikom.workIndependent engineering studio

Public data / evidence / static deliveryFive product types built and tested · production cutovers pending

Turn public sources into a product people can trust.

I build the source ingestion, fact model, quality rules, public pages, release checks, and correction path together. The result is a focused data product, not a scraped database wearing a theme.

5 source-backed product configurations · exact 50,001-page snapshot-loader test

Estimate your version
Approach
Adapted to your business
Hosting
Your server or cloud account
Starting range
$25k–$100k+
Support
Handoff or ongoing support
First useful outcome

A useful first release, built around the real job

A source-backed public product with its own fact model, publication rules, routes, interface, refresh schedule, release checks, and admin controls.

  • One primary product and audience
  • One main source family
  • Source history and conflicting facts
  • Rules for what gets published and when it becomes stale
  • Public renderer, routes, and sitemap contract
  • Release validation, activation, rollback, and runbook
Working flow

How the system fits together

  1. Official, licensed, or owned sources
  2. Entities, facts, and source history
  3. Quality checks and publication rules
  4. Immutable public snapshot
  5. Monitor, correct, and release again
Your implementation

Your version follows your business

The reusable parts give us a head start. Your version still follows your data, staff, approvals, integrations, and infrastructure—not somebody else’s generic process.

Already built

This is not a blank-slate proposal

The system supports five materially different product configurations. It records the source behind each fact, handles conflicts, applies product-specific quality and publication rules, builds immutable public snapshots, and has an exact 50,001-page loader test. All five products currently run as pre-production releases; cutover is still pending.

Wrong fit

When this is the wrong tool

  • A site whose source rights, audience, and useful decision are still unknown
  • Mass publishing without a defensible fact model or correction process
  • Guaranteed traffic, rankings, citations, leads, or revenue
Related builds

The case studies show what shipped, what was tested, and what is still unfinished.

Five products from one evidence pipelineHow one core supports different sources and admission rules. 2.18 million official observationsA repeatable national-data import and immutable Rust release. Evidence-backed review back officeCollection, scoring, approval, routes, and publication.
Project cost calculator

Build a first-pass budget

Start with the useful core, then add only the parts your version needs. The calculator updates here in your browser; nothing is submitted until you attach the estimate to an enquiry.

Useful core releaseThe included scope described above, adapted to one business and deployed into your account. $25k–$45k
Choose optional scope
Estimated one-time build $25k–$45k Useful core only
Core release
$25k–$45k
Optional scope
$0

Selected scope

  • Useful core release
Choose what happens after launch
Ongoing costHandoff — no ongoing fee
Assumptions behind this range
  • One person can approve scope and product decisions.
  • The source data is usable and available for review.
  • Deployment goes into infrastructure you control.
  • The reusable core remains mine; your data and business-specific work remain yours.

Messy data, migrations, unusual integrations, compressed deadlines, and deeper production responsibility can move the range.

Attach estimate and continue

This is a planning range, not a quote or a promise of delivery dates. I confirm scope, dependencies, and responsibility before proposing a build.

After launch

Run it yourself, or keep me around

I fix agreed-scope defects for 30 days after handoff. Then you can take over completely or keep me involved 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 release includes 30 days for defects against the agreed scope. Refresh operations, source breakage, new products, and production incidents are separate work.