Business solutions

A script for
the boring job.
Any source. Any out.

Custom scripts that move data from wherever it lives, files, sites, mail, APIs, folders, into a website, Word, a report, or the tool you already use.

Most Kenyan teams can skip a platform. They need one job done: take this, put it there, every day, without someone copying by hand. Custom scripts are that job, any input, any output, written once, run on a schedule or a button.

Any in
Files, mail, APIs
Any out
Site, docs, tools
Hours
Short of months
Yours
Source + runbook

Jobs we write

Whatever you have. Wherever it needs to go.

Into a website

Products, prices, branches, tenders, or staff lists published from a file, a form, or another site, no CMS form per row.

Into Word, PDF, or mail

Contracts, letters, certificates, packing lists, reminders, one template, hundreds of filled outputs.

Between your tools

Folder to folder, mail to a tracker, a form to accounting, WhatsApp into a log. If both sides exist, we connect them.

With a model if needed

Pair with AI automation when a step needs reading or drafting, beyond copying fields.

$ corvux script run --job nightly-sync
SOURCE inbox + folder + API
CLEAN 8 bad records skipped
WRITE website + PDF pack + notify
TIME 11s (was a Friday afternoon)
✓ next run: Monday 06:00

How it lands

Small enough to finish. Clear enough to own.

01
Show us the job
What goes in, what a good output looks like, and who does it by hand today.
02
We write the script
Python or the stack your team can keep. Sample run on a copy of your data first.
03
Button or schedule
Drop-folder, a small web form, or a nightly job on cloud or your own machine.
04
Handover
Source, a one-page runbook, and what to do when a new field appears.

This sits next to AI business solutions when the work is bigger than a script, and next to document intelligence when the input is messy PDFs.

FAQ

The usual first questions.

What can a script connect?

Anything your team already touches: files, folders, websites, Word or PDF templates, email, WhatsApp, databases, and APIs. If it has a path in and a path out, we can script it.

Do we need an API?

No. Many jobs are file in, file or page out. We add APIs when the destination already has one.

Is this AI?

Sometimes a script is the whole job. A lot of the value is a reliable script: map fields, clean records, write the output. We add a model only when a step needs language, copy, a summary, a classification.

Who runs it after handover?

You can. We leave a short runbook and a button or scheduled job. Or we keep it running on a cloud box under a monthly support line.

Describe the job

What goes in, what should come out. We will tell you if it is a two-day script or a full product.

Request a script