How it works
Karvoix helps teams move from recorded activity data to calculation, review, and reporting in one structured workflow that is easier to follow and easier to review than spreadsheet-led reporting.
This walkthrough is meant to help you compare your current reporting process with a more structured workflow.
This stays intentionally practical and human-readable so visitors can understand the workflow quickly without logging in.
Flow summary
Activity data flows into factor-backed calculation, then into review and reporting, without forcing teams to rebuild the logic across disconnected sheets each cycle.
Instead of rebuilding logic across spreadsheets each cycle, the workflow stays connected from input to reporting.
Add activity data such as fuel usage, electricity, or logistics records into one workspace instead of collecting them across disconnected sheets and file versions.
Instead of collecting files across teams before review begins.
Karvoix applies factor-backed calculations to recorded fuel, electricity, or logistics activity using region-appropriate logic where applicable, keeping the basis visible instead of burying it in formulas and side notes.
Instead of decoding formulas and assumptions after the fact.
Review headline totals, contributors, and movement over time for fuel, electricity, or logistics categories from the same product flow instead of reconciling versions manually before every internal discussion.
Instead of reconciling different versions across teams.
Create monthly reporting views and snapshots from the same structured flow, so outputs stay tied to the activity and review logic that produced them instead of being rebuilt each cycle.
Instead of rebuilding outputs every reporting cycle.
We use a 30 to 45 minute working session to walk through your current reporting flow, where spreadsheet-based review slows teams down, and how this workflow would fit in practice.
This is typically where teams see whether the workflow actually reduces review friction.
No preparation needed. Bring your current process or questions — we’ll walk through it together.
API-focused flow
For teams evaluating more than a dashboard, this flow shows how the current integration baseline compares to spreadsheet-led reporting and where developers can start with a believable scope right now.
01
Submit activity through the calculate API or CSV baseline with the facility context the record belongs to.
02
The backend calculates and persists carbon truth in one system rather than returning an isolated number with no history.
03
Read submitted activity back so internal systems and reporting flows can work from the same stored record.
04
Use ledger trace to inspect historical context and understand how the result was formed later on.
This baseline includes activity submission, facility support, activity readback, ledger trace, CSV validate/import baseline, and credential surfaces for API keys, service accounts, and webhooks.
Quickstart, API reference, and developer surfaces are shared during controlled pilot onboarding.
Quickstart, API reference, and developer surfaces are shared during controlled pilot onboarding.
Workflow gallery
This set connects facility setup, data import, dashboard review, and analysis so visitors can understand the operating path before entering the product app.
These screens show what teams actually review, not just what gets reported.
Step 01
Facilities give the workflow a clear place to start before records, calculations, and review surfaces build on top.
So teams know where the number comes from before reviewing it.
Step 02
Manual entry and CSV import both support getting real activity into the system instead of re-keying everything later.
So data is structured early instead of reconstructed later.
Step 03
The dashboard turns recorded activity into an immediate summary of totals, signals, and what deserves attention next.
So reviewers see movement without rebuilding context.
Step 04
Analysis surfaces add the breakdowns and trend context needed for serious review conversations.
So analysis happens without leaving the workflow.
What visitors should expect
That split keeps this repo focused on understanding, trust, and conversion while leaving authenticated product logic inside karvoix-web.
The goal is to understand the workflow before committing to the product.
Explain product value, workflow, trust posture, and how visitors can continue into the product app.
It does not include dashboard runtime logic, authenticated flows, or product-shell behavior copied from the app.
Getting started
This is the shortest path from the marketing site to your first real product workflow.
This path is intentionally simple so teams can move from understanding to real workflow quickly.
01
Start here to understand what Karvoix does, who it is for, and how the product workflow is structured.
02
Use the primary CTA to continue from the public site into the separate product application entry point.
03
Authentication and runtime product workflows stay in the product app rather than on the marketing site.
04
Once inside the app, create or select a facility, then start with manual activity entry or CSV import so results can be reviewed across dashboard, analysis, and reports.
Next step
Bring your current process, reporting questions, or first activity data examples. We will walk through the workflow together and show where it reduces spreadsheet-driven review friction.
Use this session to decide whether this workflow fits how your team already works.
No preparation needed. Bring your current process or questions — we’ll walk through it together.
