Software engineering · Est. Lahore
We refine raw ideas into engineered systems
Senior-led engineering. Fixed prices. Written specs. Systems you own outright.
We would rathertalk you out of it.
Sheet notes
- Scope
- Discovery, 2–4 weeks, fixed fee
- Output
- A written recommendation
- Bias
- None — the fee does not move
- Ref
- Sheet 04 — the five gates
Discovery is a fixed fee, and it ends in a written recommendation — sometimes that recommendation is “don't build.” The fee is the same either way, so the advice has no thumb on the scale.
Discovery — terminal states
02 of 02
- A
Build
With a written spec and a fixed price
- B
Don't build
With the reasoning in writing
Same fee, same deliverable, either way.
Four pillars.
Twenty-seven capabilities.
01 — Enterprise & core business
The systems the business runs on.
- 01.1ERPOne system of record for operations, replacing the spreadsheet lattice holding it together.
- 01.2CRMPipeline and customer history the sales team actually keeps current, because it costs them nothing to.
- 01.3HRMS and payrollLeave, attendance, and pay runs that close on time without a wall calendar and a prayer.
- 01.4Business intelligenceDashboards fed by modeled data, not exports — numbers two people can agree on.
- 01.5Supply chain and inventoryStock levels, procurement, and movements reconciled in one place, in near-real time.
- 01.6Custom internal toolingThe workflow software nobody sells because it's specific to how your business actually works.
02 — Customer-facing & digital commerce
Everything the customer touches.
- 02.1E-commerce ecosystemsStorefront, checkout, inventory, and fulfilment as one system — not four plugins in a trench coat.
- 02.2Native and cross-platform mobileiOS and Android from one codebase where that holds up, native where it doesn't.
- 02.3Secure portals and dashboardsCustomer and partner logins with the permissions model designed before the UI.
- 02.4CMS buildsEditors publish without a developer in the loop; the schema keeps them out of trouble.
- 02.5Product design and UX engineeringInterface decisions made in design files before they get expensive in code.
- 02.6POS and booking systemsCounter and calendar software that keeps working when the connection doesn't.
03 — Core engineering & infrastructure
Boring, observable, cheap to run.
- 03.1Cloud architecture (AWS/Azure/GCP)Sized to the load you have, priced monthly before it's provisioned.
- 03.2DevOps and CI/CDEvery merge builds, tests, and deploys itself. Releases stop being events.
- 03.3Data warehousing and lakesOne queryable home for the data currently scattered across seven tools.
- 03.4API design and integrationContracts written down first, versioned, and kept — internally and with third parties.
- 03.5Legacy modernizationStrangler-pattern migrations off systems the business can't afford to pause.
- 03.6QA and test automationRegression suites that run on every commit, so bugs surface before customers do.
- 03.7Security, hardening and complianceThreat modeling, access control, and audit trails treated as requirements, not retrofits.
- 03.8Managed support and SLAsNamed response times in writing, monitoring that pages us before you notice.
04 — Emerging technologies
Applied where it earns its cost.
- 04.1Machine learningModels in production with monitoring and retraining — or a written case for the heuristic instead.
- 04.2LLM integration and RAGLanguage models grounded in your documents, with the failure modes measured before launch.
- 04.3MLOpsVersioned data, reproducible training, and deployment pipelines — the unglamorous part that makes ML real.
- 04.4Computer vision and NLPInspection, extraction, and classification where a camera or a corpus beats a clipboard.
- 04.5IoT platforms and fleetsDevice provisioning, telemetry, and over-the-air updates for hardware in the field.
- 04.6Robotic process automationScripted hands for the systems that will never get an API.
- 04.7Blockchain and smart contractsBuilt where a shared ledger is the actual requirement — we'll say so when it isn't.
Named for metalwork. Closed in writing.
Elapsed weeks — span is typical duration
Cast is not a gap. It is most of the engagement.
01 — Assay
Hover a gate to compare
- Written recommendation — build, or don't
- Problem and scope definition
- Risk register
- Fixed-price quote, if building
Gate closes when
You hold a written recommendation and, if it says build, a fixed price against it.
01 Assay
2–4 wks
4 written deliverables
02 Smelt
2–4 wks
4 written deliverables
03 Cast
4–7 mo
4 written deliverables
04 Temper
3–6 wks
3 written deliverables
05 Finish
Ongoing
3 written deliverables
Nothing moves forward on a verbal. Every gate closes on a written deliverable you keep.
See the processFour things every engagement gets.
01
Senior-led engineering
Every engagement is architected and reviewed by a senior engineer. No handoffs to a bench you never met.
02
Transparent cadence
Working software demonstrated weekly or fortnightly. Progress is something you watch, not something you're told about.
03
Systems that outlive us
You own the repositories. No proprietary runtime, no lock-in, nothing that stops working when the engagement ends.
04
Documentation in scope
Docs are a deliverable, not a favor. The next team — even if it isn't us — starts from a written system, not an archaeology dig.
Structural facts
No history claimed
Capabilities
0
across four pillars
Gates
0
none passed on a verbal
Hourly invoices
0
we don't bill by the hour
Cadence
1–2 wks
working software, demos included
Boring where it should be. Sharp where it counts.
Selection rule
- Default
- The dull option that already works
- Exception
- Where the problem genuinely needs it
- Never
- Because it looks good on a CV
- TypeScript
- Python
- Go
- Rust
- React
- Next.js
- React Native
- Flutter
- .NET
- Spring
- Node.js
- Django
- Postgres
- MySQL
- MongoDB
- Redis
- ClickHouse
- Kafka
- RabbitMQ
- dbt
- Airflow
- AWS
- Azure
- GCP
- Kubernetes
- Docker
- Terraform
- GitHub Actions
- Grafana
- Prometheus
- PyTorch
- TensorFlow
- LangChain
- pgvector
- OpenSearch
- Elasticsearch
- Stripe
- GraphQL
- gRPC
- Playwright
Next — Start with discovery
Bring us the raw idea
Discovery is a fixed fee. The recommendation is honest — even when it's “don't build.”
What follows
- 01
- Reply within 2 business days
- 02
- 45-min scoping call
- 03
- Fixed discovery quote