Service / Corporate software
I build custom software for purchasing requests or IT support and asset custody, shaped around how your business works. Define a first release around one process and a small group of users.
Explore two starting pointsThe demos below use fictional records in browser memory. They do not provide real accounts, persistent storage or live client applications. The delivery scope describes an application to be developed for your needs.
For businesses where requests pass between employees, managers and a purchasing owner.
Request lines, revisions, an agreed manager approval, orders, partial receipts and activity history.
Acceptance example: changing an approved request requires renewed approval; an order cannot close while quantities remain unreceived or uncancelled.
Try the working demo — Purchasing and approvalsFor teams that assign devices to employees and have someone responsible for support and maintenance.
Asset records, assigned users, issues, repair stages, loan devices and handover history.
Acceptance example: ownership and physical location remain separate; a job cannot close until the loan device return is recorded.
Try the working demo — Support and asset custodyFirst delivery scope
Define the initial module, user groups, visible records and approval permissions in writing.
Sign-in, server-side access controls and persistent records are developed for the delivered application.
Apply your approval, rejection, revision, receipt and cancellation rules, with actor and time records.
Agree on pending work views, status filters, reports and Excel-compatible exports.
Scope migration with an anonymized sample; include backups, restore checks and responsibilities in the delivery plan.
Validate acceptance scenarios with a small group; agree user guidance, account and data ownership and source usage rights.
Multi-level approvals, accounting or ERP integration, inventory valuation, e-signatures, automatic messages and single sign-on are evaluated separately. Fees and timing are quoted once users and scope are agreed.
Working together
Walk through a request or issue: who starts it, who decides and where does it wait?
Select the module that fits. Define users, functions, exclusions, fees and acceptance criteria in one proposal.
Try the agreed scenarios and check permissions, revisions and incomplete-work rules.
Separate setup/development fees from optional maintenance. Define the defect-fix period, support hours and pricing for new requests.
First conversation
For the first conversation, bring someone who knows the process, an anonymized form or file, an approximate user count and the step you find most difficult.
Discuss corporate software(new tab)