CRA reporting
Get ready for Article 14
If a bug in your product is being exploited, you have 24 hours to send an early warning. On a delivery date agreed in writing, we set up who does it on your product.
CRA overviewSamisoftz is a custom software development studio in Lahore, Pakistan.
We get your product ready for the CRA's 24-hour warning on a delivery date agreed in writing, build the store your theme can't, and put AI into the tools your team already uses.
30 minutes, no slides.
100% of the source code in your GitHub. Milestone approvals. Zero lock-in.
6,000+active users on an AI SaaS we worked on
Code ownership
Code, docs and access stay in your name.
Founder-led
Usama takes the call and writes the code.
Apps live in production
Shops, tools and platforms we've worked on.
CRA reporting
If a bug in your product is being exploited, you have 24 hours to send an early warning. On a delivery date agreed in writing, we set up who does it on your product.
CRA overviewE-commerce
Custom storefronts, shows people can buy from, stock that matches across marketplaces, and an admin your team works in.
E-commerce overviewAI implementation
Automation for the work done by hand, chatbots that hand over to a person, and AI connected to your CRM or store. Tested on your own examples before launch.
AI overviewFour problems we keep seeing, and what we do about each one.
01
You explain the job to someone senior. The repository is then written by people you never meet.
Usama writes the code on every project. He is also the person on your call. There is no sales rep in between.
02
If a bug in your product is being exploited, you have 24 hours to send an early warning. If nobody owns that send, the window can close while people look for the right document.
We set up who decides, what to send and when, on your product, and practise it once with your team.
03
The shop takes orders. It still can't do the next thing you need: a live show, stock that matches across marketplaces, or an admin your team works in.
We build a custom shop or back office, and it goes live on a date we agree in writing.
04
A chatbot or automation goes live after a good demo. Nobody checked it on real cases, so the team stops trusting it.
We test it on your own past examples against a pass bar you agree first, and keep a person on the steps that cost money.
Named from past builds, not a wish list. Each tab shows where we used it.
Sites, storefronts and admin panels, plus a phone app for iOS and Android.
Used on
APIs, background jobs and the logic behind the admin.
Used on
Orders, users and documents, in a database you own.
Used on
Card payments, splits between sellers, payouts and invoices.
Used on
Live video, chat and stock counts that update as they change.
Used on
AI only where it cuts a real task, like reading a PDF or drafting a document.
Used on
Running in your accounts, not ours.
Used on
30-minute call. You'll know if we can help.
No obligation
Written scope and a fixed price.
Scope and price in writing
A staging link, or the first runbook draft, in your tools.
In your tools
You see what changed before the next piece starts.
You see it before the next piece
We run it with your team once. Code, docs and access are yours. We stay on call for 30 days.
Code in your accounts
A few of the products we've worked on. Open one to see what it does and how it works.

Live shopping
Viewers check out without leaving the stream.
Live video with chat, a cart viewers build together, payments, invoices and the admin behind it.

Car hire
The public site and the admin sit together.
The public site and the admin the team uses to run it.

AI SaaS
People keep using it.
Accounts, billing and the screens people practise in. It is live.

Documents
A PDF becomes rows.
A statement PDF goes in. Rows a spreadsheet can use come out.

Video
A clip, ready to export.
Pick a stretch of a video and export that clip.
Usama
Founder, Samisoftz
I'm Usama. I write the code on every project and I'm the person on your call.
You do. Code written for you goes into your GitHub. We may reuse our own building blocks, such as clock logic and export templates. If we do, you get a licence to use them for as long as you run the software. Everything written for you is yours.
If the job is clear enough to price, you get a written scope and a fixed price. If it is not, we say so on the call. When you want the scope written before a build, that is a paid brief you own: what is in, what is out, and a price. Hire us to build it, or take the brief elsewhere. The first call is free.
The first call is free. The price is written down before the build, in stages you approve. You see what changed before the next stage starts. We don't put a rate on this page.
We run it with your team once. Code, docs and access are yours. We stay on call for 30 days.
No. You talk to Usama. He writes the code on every project and he takes the call. Samisoftz is a small team, so we take a few jobs at a time.
You'll talk to Usama, who'd build it.
30 minutes · no slides · a written answer if it's not a fit