Five kinds of work, and they overlap more than the headings suggest. Every one of them has ended up needing an API, a permissions model and somebody who will read the accounting rules properly.
ERP and business software
Multi-tenant ERP systems, from the chart of accounts up.
The systems a business runs its operation and its books on. I have built these as a sole engineer, which means the accounting is mine as well as the code, and the two have to agree.
- Double-entry accounting, chart of accounts, party ledgers and banking
- Inventory, purchasing, sales, production and consumption
- Multi-tenant architecture, built to onboard client tenants without a fork per client
- Roles and permissions as a matrix, granular per module and per action
- Migration off legacy systems, including the data cleanup nobody scopes for
- Tax compliance integration, including FBR digital invoicing
Web applications
Full stack applications in Laravel, Vue, React and Next.js.
Applications with real users and real state behind them, rather than sites. Server rendered where that is right and a single page app where it is not.
- Laravel and PHP on the server, Vue.js, React or Next.js on the client
- Real-time features over Pusher, for chat and live state
- Payment integration with Stripe and PayPal
- Reporting and dashboard interfaces that print as well as they render
Backend systems and APIs
REST APIs, business logic and database design, in PHP and Java.
The half of the system nobody sees. Schema design, the rules that sit on it, and an API stable enough that two or three separate frontends can be built against it at once.
- REST API design, versioned and documented enough to hand over
- Java and Spring Boot services, with Hibernate over Oracle
- Database design and query work in MySQL and Oracle SQL, including production debugging
- Background processing, imports and reconciliation jobs
Client portals
Separate portals for separate audiences, on one backend.
One system, several kinds of user, and a different set of things each of them is allowed to see. This is most of what a B2B platform actually is.
- Multiple dashboards against a shared API, with permissions worked out per audience
- Superadmin tooling for the team that operates the platform
- Onboarding, subscription and billing flows
- Real-time messaging between the parties in the system
Financial systems
Payments, KYC and cash flow, in production.
Work where correctness is the feature. Built on banking infrastructure serving a national payment application and one of Africa's largest banks.
- Payment processing and cash flow modules
- Customer KYC workflows and the back office queues behind them
- Payment gateway integration and reconciliation against internal ledgers
- Production incident tracing through SQL on live data