Custom software
Application modules, APIs, data models, and release pipelines delivered against a signed scope list.
Art. 00 · Engagement folio
Custom software, written as a statement of work
Zealio Solutions LLC builds and advises on enterprise applications for B2B buyers. The opening visual is the delivery bench: a left monitor with a code editor and source files, a right monitor with labeled architecture boxes for API, database, queue, and web app, a keyboard, and a notebook of module notes.
3Practice lines
6Build modules
4Data entities
SOWScope on paper
B2B IT consulting
Field maps, package options, and sequence plans for ERP, CRM, and adjacent ledgers already in use.
Enterprise solutions
Operations dashboards, QA evidence, and security control checklists that sit with the live system.
Art. 01 · Discovery
Scope, modules, and acceptance on paper
Kickoff starts with a printed Statement of Work. Headings cover Scope, Modules, and Acceptance. A numbered module list sits on the page, a tablet repeats the same outline, and a black pen marks the working copy.
- Scope — in-scope screens, jobs, and interfaces; out-of-scope items listed beside them.
- Modules — named application pieces with owners and target increments.
- Acceptance — test IDs that must pass before a release is signed.
Art. 02 · Construction
Source in the editor, six named modules
Build work happens in a code editor with a file tree on the left and application source on the right. The six modules below are the usual first increment for a trade or operations buyer.
Accounts
Company records, roles, and sign-in for buyer staff.
Orders
Order capture, status, and line quantities.
Catalog
SKU lists, units, and price books used by sales desks.
Invoices
Invoice headers, due dates, and payment states.
Jobs
Background jobs for imports, exports, and queue work.
Admin
Configuration screens for flags, users, and audit rows.
Art. 03 · Interfaces
REST paths on the OpenAPI page
External systems call documented endpoints. The documentation screen lists paths such as /orders and /customers, HTTP methods GET, POST, and PUT, and JSON request and response examples.
- GET — read customer or order records.
- POST — create an order or customer payload.
- PUT — replace fields on an existing record.
Art. 04 · Consulting
ERP fields mapped to CRM fields
Advisory work is a spreadsheet, not a slide. One column group lists ERP fields; the other lists CRM fields. Rows pair source and target so a cutover does not invent a third ledger.
The data model on the right is the same four entities used in build: Customer, Order, Invoice, and Payment, drawn as rectangles with key fields and connecting lines.
Art. 06–08 · Evidence
Test IDs, pipeline stages, live tiles
Enterprise delivery keeps three artifacts in the same folio: a printed QA report, a CI pipeline screen, and an operations dashboard.
Art. 09 · Controls
A checklist, not a padlock graphic
Security work is recorded as named controls. The printed sheet includes Access review, Backup test, and Encryption at rest, each with a checkbox column the operator ticks after evidence is filed.
- Access review — role list versus active accounts.
- Backup test — restore drill dated on the sheet.
- Encryption at rest — store setting confirmed for the database volume.
Buyers
Who signs the same folio
Manufacturers
Order, catalog, and invoice modules tied to an existing ERP field map so plant desks do not re-key shipments.
Distributors
Customer and order APIs with GET, POST, and PUT, plus a queue job list for nightly price-book loads.
Professional firms
Accounts, admin, and an operations dashboard for open tickets, uptime, and queue depth on internal tools.
Packages
Three ways to buy the work
Packages are statements of work, not boxed licenses. Mix is allowed; the table is the buying file.
| Package | Includes | Primary artifacts | Typical span |
|---|---|---|---|
| Build | Six modules, OpenAPI paths, ER model | Code editor increment, /orders and /customers docs, four-entity diagram | 8–14 weeks |
| Advise | ERP–CRM field map, sequence, cutover notes | Spreadsheet map, SOW with Scope / Modules / Acceptance | 3–6 weeks |
| Run | QA IDs, CI stages, ops tiles, control sheet | Pass/Fail report, Build–Release pipeline, dashboard, checklist | Retainer |
FAQ
Before you send a brief
Do you sell a boxed product?
No. Work is scoped as custom software, consulting, or a run package against your systems.
Can you start from an existing ERP?
Yes. The ERP–CRM spreadsheet is the usual first consulting artifact so fields are paired before code is written.
What does a first increment contain?
Accounts, orders, catalog, invoices, jobs, and admin — the six modules shown beside the editor.
How is acceptance proven?
Printed QA rows with Test ID and Pass or Fail, plus green checks on Build, Test, Stage, and Release.
What sits in production?
The operations dashboard (open tickets, uptime, queue depth, request-volume chart) and the control checklist.
Do you staff an on-site team?
Engagements are remote-first with scheduled reviews. On-site workshops are quoted only when the brief asks for them.
Brief
Send the systems you already run
Name the ERP or CRM, the modules you need, and whether you want Build, Advise, or Run. A scoped SOW is returned before any code starts.