Business systems · Internal tools · Integrations
Build around the way your team works.
If requests live in email, files sit in different folders and someone keeps copying the same data, show me the process. I help you decide whether to connect the tools you have or build a system for the work.
Follow a request from arrival to report
Illustrative example, not client work- 01Request
- 02Assign
- 03Review
- 04Report
Request
Assign
Review
Report
The request arrives with what your team needs, instead of scattering the details across messages.
Walk through a real request
We follow one piece of work from the moment it arrives to the moment it is finished. Who handles it? What do they need to see? Where does it wait, and who can change it?
Use a redacted example. I don’t need private customer records to understand the workflow.
Internal tools, portals and document workflows
The build might bring requests, assignments, approvals and reports into one place. A customer portal can let people submit information or follow a request without asking your team for each update.
For document processing, we define what should be extracted, what needs a person’s review and what happens when the result is incomplete. We test those cases, not just a clean sample.
Connect before replacing
An existing system may only need an integration or a small addition. We check its export options, APIs and access restrictions before proposing a replacement.
If you need standard accounting or an off-the-shelf ERP, we should consider existing products first. Custom development makes sense when there is a specific gap worth building for.
Test with the people who will use it
Your team reviews working versions during the build. We check permissions, incorrect inputs, repeated actions and the process for correcting mistakes.
We agree on deployment, data transfer where required, account access, documentation and support. A system that handles regulated or sensitive information may also need specialist review; we identify that in the scope.
Relevant work
My work includes inspection and reporting systems, document extraction and review tools, and internal tools and integrations for Lululili. Not all of those systems can be shown publicly.
I can explain the approach without exposing client records. The Work page distinguishes public projects from that broader experience.
Questions before starting
Do we have to replace our current system?
No. We first check whether a configuration change, integration or existing tool can solve the problem.
Can AI help with our documents?
Possibly. We need representative, redacted samples, a definition of acceptable output and a review process for mistakes. We decide whether AI is appropriate for the task rather than add it by default.
How is the work estimated?
We define the workflow, roles, integrations and handover requirements. Agreed work is billed at SAR 250/hour for actual time, with third-party costs separate. You review the scope before we begin.
Show me where the work gets stuck.
Describe one process, the tools involved and what you want to change. Leave out passwords and confidential records.