Every question, one place, direct answers.
Company, engagements, the Standard, products, security, pricing — the questions we get asked most, answered in full on this one page instead of scattered across a dozen others.
This page collects the questions people actually ask before, during, and after working with Qawex — grouped into six topics below. Every answer that references a rule from the Qawex Standard uses the real rule ID, so it can be checked against the service page that rule governs, not just taken on faith.
Browse by topic
Jump straight to the section that answers what you came here for.
What does Qawex Solutions actually build?
AI systems and software for organizations handling sensitive data — agents, automation, custom platforms, document workflows, and security hardening, organized under five pillars: Intelligence, Engineering, Cyber, Paperless, and Growth.
Is Qawex a healthcare company?
No. Healthcare is where we've proven the work — our HealthTech Suite is real case-study depth — but it's proof of the approach, not the category we're limited to. The same Standard applies whatever the industry.
What's the difference between Qawex Solutions and Qawex the product?
Qawex Solutions is the company. Qawex (under Products) is a platform product the company builds and maintains — one offering among the services, managed packages, and free tools Qawex Solutions delivers.
Where is Qawex based, and who do you work with?
We build Pakistan-first digital products and also take on client engagements more broadly — clinics, dental practices, and organizations that need software built around real operational constraints, not a generic template.
How does a project actually start?
With scope, not a sales deck. We map which rules in the Qawex Standard apply to what you're building before any work begins, so the engagement has a checkable boundary from day one.
Do you only build from scratch, or work on existing systems too?
Both. Rapid MVP Development covers new builds; Legacy Modernization and Systems Integration & APIs cover working inside what you already have, including a strangler-style migration where a full rebuild isn't the right call.
What does handover look like at the end of an engagement?
Documentation mapped to the rules that governed the build, access handed over cleanly, and no dependency left on us to keep the system running unless a managed arrangement is explicitly part of the scope.
Can you work alongside our in-house engineering team?
Yes — engagements are scoped around what you need, whether that's a full build, a focused audit, or embedded work alongside an existing team.
What is the Qawex Standard?
A fixed set of 63 numbered rules across five pillars that every engagement is built against — each rule has an ID, a plain statement, and, where possible, an enforcement or test. See the full breakdown on The Qawex Standard.
What happens when a rule can't be followed exactly?
The exception is published with its own ID, a stated scope, and a logging requirement — like INT-01-EMERGENCY, which narrows the human-approval rule for time-critical medical escalation. It's never bent quietly.
Is the Standard specific to one industry?
No. The same 63 rules apply to a healthcare platform, an internal tool, or a client's e-commerce system — the pillars (Intelligence, Engineering, Cyber, Paperless, Growth) are industry-agnostic by design.
Can I ask which specific rules apply to my project?
Yes — that mapping happens during scoping, before work starts, and the relevant rule IDs are cited on the deliverables they govern once the build is live.
What's the difference between Services, Managed Packages, and Products?
Services are individual engagements under the five pillars (e.g. Intelligent Document Processing). Managed Packages are bundled, vertical-specific offerings like Dentist Solutions. Products are standalone platforms Qawex builds and runs, like the Qawex platform itself and the HealthTech Suite.
What's included in the HealthTech Suite?
Hospital Management, Clinic Management, Telemedicine, and Appointment Booking — each positioned for a different scope, from a full hospital system down to a standalone booking layer.
Are the Free Tools actually free, no catch?
Yes. Tools like First Aid have no account requirement and no cost — they exist because they're useful on their own, and using one doesn't commit you to anything else Qawex offers.
Who can actually access our data once a system is built?
Access is enforced at the database level, per CYB-01 — not just hidden behind a menu in the interface. Role and department boundaries hold even if someone bypasses the front end.
How do you verify that access controls are actually working?
By querying the system directly rather than inspecting configuration screens — CYB-02. A control that looks correct in a settings panel isn't verified until it's been checked against real data.
What happens if an automated system fails partway through a task?
It's required to fail loudly, not silently — INT-08. A system that fails without telling anyone is worse than no automation at all, because the person downstream assumes it worked.
How is a project priced?
Scoped per engagement rather than off a fixed rate card — what you're building, which pillars it touches, and how many Standard rules apply all factor into the quote.
Is a security audit priced separately from the fixes it finds?
Yes, deliberately. Hardening work is quoted separately from the audit itself, because an audit that exists to generate its own remediation work isn't an honest audit.
Do Managed Packages and Products have recurring costs?
Managed Packages and hosted Products typically involve an ongoing component since they include upkeep; one-off engagements under Services generally don't. Specifics are confirmed at scoping.
Didn't find your question?
Ask us directly — if it's a good question, the answer usually ends up on this page next.
Ask a question