Software Division

Portfolio & capabilities

Internal and desktop work is often private. Here is how engagements are shaped—and where you can see public-facing builds.

Types of software shipped

  • Desktop & line-of-business — Windows-first utilities, intake forms, label or receipt printing, and packaged installers your IT can whitelist.
  • Automation & integrations — Scheduled jobs, folder watchers, CSV/API ingestion, ERP or accounting bridges, and alert paths to WhatsApp or email when something breaks.
  • Internal dashboards — Role-based screens, KPI tiles, drill-down tables, PDF/Excel exports, and audit-friendly activity logs.
  • Workflow hardening — Turning fragile spreadsheets and chat-based handoffs into governed steps with validation, ownership, and rollback-friendly data rules.

Web & marketing sites

Public sites, landing pages, local SEO, and performance-led builds ship under the Web Division. Pair them with Software Division when you need a public site and an operations console.

Open web portfolio

Code & experiments

Public repos and experiments show how problems are broken down, how APIs are wrapped, and how small tools are structured before they grow into full products.

GitHub profile

How a software engagement runs

No mystery phases—each step has a deliverable you can review, reject, or refine before the next invoice slice.

01

Discovery

Map the workflow, inputs, failure modes, and who owns each handoff. Output: written scope, risks, and milestone plan.

02

Build

Vertical slices with demo builds early—so you see real UI and data paths, not slides. Output: testable increments per sprint.

03

Harden

Logging, backups, installer signing where applicable, and operator training. Output: runbook + short Loom walkthroughs.

04

Handoff

Source, credentials vault export, and a 30-day warranty window. Optional retainer for changes, monitoring, and new integrations.

Capability snapshots

Representative shapes of work—client names omitted, details generalized for confidentiality.

Distribution

Dispatch & invoicing desk

Desktop console merging orders from WhatsApp exports and an accounting CSV, with printable manifests and exception queues for partial shipments.

  • · Offline queue when connectivity drops
  • · Role: dispatcher vs. accountant approvals

Operations

Recurring file & API bridge

Nightly jobs pulling supplier price lists, normalizing SKUs, diffing changes, and posting summaries to email with rollback snapshots.

  • · Alerting on schema drift
  • · Human-readable audit trail

Leadership view

Executive KPI strip

Read-only dashboard fed from a guarded database view—margin by category, stock aging, and SLA breaches without exposing raw PII.

  • · Export to PDF for board packs
  • · French / English labels

Stack & integration surface

Picks depend on your constraints—not trends. Common combinations include desktop shells (Electron, Tauri), services in Node or Python, SQLite or PostgreSQL, Supabase when a hosted backend fits, and Redis or file locks for job coordination.

REST / SOAP Webhooks WhatsApp Cloud API SMTP / SendGrid SFTP drops Windows services Scheduled tasks SSO-ready auth

Have a reference workflow or a rough spec? That is enough to start a discovery call—NDA-friendly when needed.

Next step

Share a workflow sketch or a short Loom—rough notes are fine. I will reply with what is realistic to ship first and how it fits your timeline.

Contact View pricing