Response times
Working days are Monday to Friday, Pakistan Standard Time (UTC+5). We work with clients across time zones; these are the commitments regardless of where you are.
| You send | We commit to |
|---|---|
| A project enquiry or a completed project brief | A reply from a person within one working day — not an auto-responder |
| A booked consultation | Immediate confirmation with a calendar invitation; the slot is held the moment you book it |
| A question from an active client during delivery | Same working day, and a decision or an owner by the next |
| A production problem on a system we built and support | Acknowledged within four working hours, with a status update until it is closed |
| An accessibility problem on this site or on work we delivered | Acknowledged within three working days, then a fix or a dated plan |
| A security report | Acknowledged within one working day; no legal threats for reporting in good faith |
If we are going to miss one of these, we say so before the deadline rather than after it.
Measured, not claimed
Every enquiry that reaches this site is timestamped when it arrives and again when it is first answered by a person. This is that record:
Measurement is running. Every enquiry is timestamped on arrival and again when it is first answered, and the median appears here once there are at least 5 measured replies — currently 0. Recording started on 30 September 2026. We would rather show you nothing than a figure drawn from three data points.
Consultation availability
Consultations run Monday to Friday, 10:00–18:00 Pakistan Standard Time, in thirty-minute slots with at least twelve hours’ notice. The booking page shows genuine availability read from the calendar — never a form that promises a call someone still has to arrange. If nothing there suits your time zone, say so and we will find a time outside the published window.
Performance, measured here
We are a studio that sells fast, well-built software, so our own site should be able to prove it. These are Core Web Vitals collected from real visits to astackra.com — not a laboratory score from a testing tool, and not a screenshot from a good day.
Measured on this site · last 28 days · 45 real visits
Good / needs improvement / poor, against Google’s own thresholds. Collected without cookies, without a third-party analytics script, and without tracking anyone across sites.
Availability and monitoring
This site runs automated health checks on a schedule: pages, the booking endpoint, the search index, outbound email delivery and the certificate chain. When a check fails, an alert reaches a person. The current state is published rather than kept private:
Live system status
Reduced capability.
Checked automatically every fifteen minutes from outside the application. Last check 1 second ago · 100% healthy across the recorded window.
- WebsiteEvery page is being served normally.Operational
- Project form and contactEnquiries can be submitted.Operational
- Enquiry deliveryEnquiries are stored and delivered to the team inbox.Operational
- NOVA assistantThe language model is unavailable, so NOVA is answering from our knowledge base and routing to a human.Reduced capability
- Search and AI feedsSitemap and llms.txt are being served to search engines and AI crawlers.Operational
These states are written by our own monitoring, not by hand. If something here says reduced or unavailable, it is because it genuinely is — and an engineer has already been paged by email.
How we behave during delivery
- Scope is written down. What is in, what is out, and what happens when something moves between the two.
- Estimates come with their assumptions. When an assumption turns out to be wrong you hear it that week, not at the end.
- You see working software early and often, not a demo assembled the night before a milestone.
- Decisions are recorded. Architecture choices, trade-offs and the reasons for them are written down and handed over with the code.
- You own what you paid for — source code, infrastructure definitions, prompts and evaluation data — and you can take it elsewhere without asking permission.
- Bad news travels fast. A slipped date told early is a scheduling problem; told late it is a trust problem.
Where AI is and is not used
We use AI in our own delivery, and we will tell you where. What we do not do: send your confidential documents to a model without your agreement, let a model take a binding action without a human approving it, or present machine-generated work as hand-reviewed when it has not been reviewed. Client systems we build follow the same rule — a person is accountable for every consequential step, and the audit trail shows who.
What we do not promise
A commitment nobody can miss is not a commitment:
- We do not offer twenty-four-hour support as standard. If your system needs it, it is a separate agreement with a separate cost, and we will say so rather than quietly hoping it never comes up.
- We do not promise a specific search ranking, lead volume or conversion rate. Anyone who does is guessing with your money.
- We do not promise that an AI feature will reach a given accuracy before we have seen your data. That is what a sprint is for.
- We do not take every project. If your problem is better solved by software you can buy, we will tell you that.
Holding us to it
If we miss one of the commitments on this page, write to hello@astackra.com with the date and what happened. It will reach the founder, and you will get an answer about what went wrong. See also the build log and the accessibility statement.
Related