Actual work, what it did

What we've built

Government · Blockchain
5moconcept to production

Sovereign token wallet for a provincial government

A private-blockchain wallet that turns a public incentive program into USD-pegged digital tokens — built and shipped in five months.

View the full case study

The challenge

The Government of the Province of San Luis, Argentina had run a successful student graduation-incentive program since 2010, offering a financial award to every student who earned their high-school diploma. It worked: provincial graduation rates climbed roughly 20%, positioning San Luis above the national average.

The Volkom approach

Volkom created Billetera Activa, a private-blockchain platform that replaces paper graduation certificates with digital tokens backed 1:1 by the U.S. dollar. Because the tokens are USD-pegged, their value is preserved regardless of peso devaluation — whether a student redeems immediately after graduation or saves for months.

Outcomes at launch

  • 100%Eligible recipients created and verified accounts
  • 84%Of issued tokens were actively redeemed
  • 25%Voluntarily chose to save rather than cash out
  • 100%Security, fraud-detection & compliance objectives met
Enterprise · Beverage
2,500+distributors served

A re-platformed distribution portal for 2,500+ distributors

For a leading beverage distributor: a customer-facing portal rebuilt on React + Enterprise ODOO that keeps 2,500+ distributors ordering across multiple countries without downtime.

View the full case study

The requirement

More than 2,500 distributors across several countries place orders through that portal. Any downtime or friction translated directly into lost sales — so reliability and performance, not new features, were the real requirement.

The Volkom approach

We worked the portal in two stages. Version 1 hardened and extended the client's internally built platform on Python and Django, for solid, reliable order handling from day one.

Outcomes

  • Customer experience
  • Reliability
  • Business continuity
  • Scalability
960hours/month eliminated

Bank collections across 6 portals

From 12 people doing manual work to a fully automated pipeline

The challenge

A company was processing collections from six different banks manually. Two people per bank, four hours a day, every day. The work was repetitive, error-prone, and impossible to scale — any new bank relationship meant hiring more people.

How we built it

We started with the highest-volume bank to prove the model, got it running in production within three weeks, then rolled out the remaining five portals over the next month. Each agent was tuned for the specific portal's UI and login flow.

What we built

We built a set of front-end automation agents — one per bank portal. Each agent logs in, navigates the portal, extracts payment data, and downloads the records. A reconciliation agent then matches everything against internal records and flags discrepancies. The entire flow runs unattended, on a schedule.

Results

  • 960 hours/month of manual work eliminated
  • Fewer errors in reconciliation
  • Faster cash visibility — data available same day instead of next day
  • Every run tracked and auditable in Mesh

How Mesh monitors this

All six agents report to Mesh. The ops team sees a single dashboard with run status, records processed, and error rates per bank. When one bank changed their portal layout, Mesh flagged the failure immediately and we patched the agent the same day.

240hours/month recovered

Order status updates in supplier portal

A team of four doing 3 hours of repetitive navigation, replaced by one agent

The challenge

Updating order statuses in a supplier portal required a team of four people, three hours every day. They had to log in, navigate to each order, check the status, update the internal system, and move to the next one. Hundreds of orders, every single day.

How we built it

The agent was prototyped in one week using a recording of the manual workflow. We iterated with the operations team to handle edge cases (partial shipments, cancelled orders, portal maintenance windows) and deployed to production in three weeks.

What we built

We built an agent that navigates the supplier portal exactly like a person would — login, search, read status, extract data — then pushes the updates to the internal system automatically. It handles pagination, session timeouts, and retries on its own.

Results

  • 240 hours/month of manual work recovered
  • Full traceability — every order update is logged with timestamp and source
  • Status updates available within minutes instead of hours
  • Zero missed updates since deployment

How Mesh monitors this

The agent runs on a schedule and reports every execution to Mesh. The team gets a daily summary of orders processed, statuses changed, and any orders that need manual review. If the portal is down or the login fails, Mesh alerts the team and us simultaneously.

80+hours/month saved

Cross-system data entry automation

Dozens of hours per week of copy-paste work, gone

The challenge

A team was spending dozens of hours every week manually re-keying data between systems that didn't talk to each other. Information from one platform had to be copied, reformatted, and entered into another — every time with the risk of typos, missed fields, and stale data.

How we built it

We mapped every field and transformation rule with the team, built the agent with full validation and error handling, and ran it in parallel with the manual process for two weeks before cutting over. The team reviewed exceptions only.

What we built

We built a system automation agent that reads data from the source systems via APIs and file exports, transforms it to match the target format, validates it against business rules, and pushes it into the destination system. No human in the loop for the standard flow.

Results

  • 80+ hours/month of manual data entry eliminated
  • Cleaner data — validation catches errors humans missed
  • No supervision required for standard flows
  • Telemetry on every run — records processed, errors caught, duration

How Mesh monitors this

Every sync run is tracked in Mesh with full metrics: records read, records written, validation errors, duration. The team has a weekly report generated automatically. When the source system changed an API field, the agent caught the mismatch, logged it in Mesh, and we fixed it within hours.