Engagement handbook

How we work with manufacturers: what each stage includes, how we access your data, what you own at the end, and where the limits are.

Avenvero is a software development studio for manufacturers and industrial companies. Every build sits on our reusable foundation (React, Python and SQL) on top of the systems you already run. We don't replace your ERP and we don't build every dashboard from scratch. Each engagement is a defined project that we deliver, validate and hand over.

We work with Australian precision engineering, machining, fabrication, industrial components and other job-based manufacturers, typically 20 to 200 people. The buyer is usually the owner, operations leader or finance manager.

Engagement process

1. Discovery call. Free, 20–30 minutes. The costly problem, your systems, source access, data readiness, who decides, and the right first module.
2. Data & systems audit. A fixed-fee diagnostic that ends in a fixed-scope proposal.
3. Statement of work. A module-specific, fixed-price scope with acceptance criteria.
4. Access and security review. Read-only credentials on agreed infrastructure.
5. Adapter and configuration. We connect your source and configure the module.
6. Reconciliation and acceptance testing. Numbers checked against your systems with your team.
7. Documented handover.
8. Optional expansion. More modules, integrations or support, only when they pay.

The data & systems audit

A fixed-fee assessment for a single site or business unit. Larger, multi-system assessments are quoted separately. It typically takes 3–7 working days once access and stakeholders are available.

• Stakeholder interview
• Source and permissions inventory
• Data quality and integration feasibility review
• KPI selection and module recommendation
• High-level security and infrastructure risks
• Fixed-scope implementation proposal and roadmap

The audit is diagnostic. It is not a formal cybersecurity assessment, penetration test or implementation. The fee may be partly credited against a signed implementation.

Initial installation

One module, connected to one compatible read-only source.

Base scope

• One approved data source or export, with an adapter and limited schema mapping
• Reusable SQL model and one selected module
• Agreed KPI definitions, up to four standard KPIs
• Scheduled refresh, portal access controls and basic monitoring
• One training session
• Deployment, handover and defined acceptance tests
• 30-day limited defect correction

Typical delivery is 2–4 weeks once credentials, clean sample data and approvals are in place. That is an objective, not a guaranteed deadline.

Architecture

The platform is built once and configured for each client, so your project is mostly configuration, adapters, mappings and agreed KPIs.

• Sources: ERP, SQL Server or PostgreSQL, production records, approved spreadsheet exports, supported APIs.
• Data foundation: Python adapters (read-only by default) feeding canonical manufacturing SQL models for orders, jobs, labour, inventory and costs, with scheduled ingestion, reconciliation, validation and logging.
• Modules: Operations, Job profitability, Inventory & purchasing.
• Portal: one React front end with shared sign-in and navigation. Only your chosen modules are deployed.

The default stack is SQL Server or PostgreSQL, Python/FastAPI and React. A cloud data warehouse is used only where it is justified. Power BI is not a standard deliverable.

Data access & security

• Read-only access to source systems by default. Writing back is a separately scoped project.
• Secrets handling, role-based access, audit logging and backups are part of the foundation.
• Documented deployment, preferably on infrastructure you own.
• Credentials, hosting, backup and support responsibilities are written into the contract.

Scope guardrails

Fixed prices hold because the standard scope has clear conditions.

Ownership

Your data, configuration and agreed deliverables are yours. The reusable platform code is licensed to you as background IP. Exit, credentials, hosting, backups and support are set out in the contract, so your own team can run the system without us.

After handover

Ongoing support is optional. If you want it, managed care covers agreed monitoring, a patch schedule and a defined allowance for small changes, with hours, response targets and exclusions written into the agreement. There is no unlimited work or 24/7 SLA by default.

Further modules, connectors, workflow automation and complex ERP integrations are scoped as separate projects. We don't do full ERP replacement and will point you to specialists who do.