Agency Hosting Budget Pakistan: PKR 5,000, 15,000 aur 40,000 Illustrative Envelopes

An agency hosting budget Pakistan worksheet names three illustrative monthly budget envelopes: PKR 5,000, PKR 15,000, and PKR 40,000. Each envelope is a monthly sum on an internal sheet. The figures are not current Adiba plans or market quotes. Every envelope is built from four assumptions: infrastructure, backup, support labor, and contingency. What the envelope can cover depends on real quotes for those four lines. Until a vendor's paper replaces an assumption, the split only proves that the parts add up. It does not state a disk size, an account count, a license entitlement, or a continuity target.

Editorial review date: 10 October 2026. The original publication date is unchanged.

Build an agency hosting budget Pakistan envelope from four lines

An envelope is the rupee total held for one client for one month before a figure is repeated outward. The PKR 5,000 envelope, the PKR 15,000 envelope, and the PKR 40,000 envelope share the same four lines. A larger sum is a larger set of assumptions, not a size tied to the price.

Infrastructure is the assumption for the invoice that rents where the sites run. Record the rupees, and leave memory, cores, disk, and account counts on the quote that names the unit. Backup is the assumption for copies: storage, the job fee, and any separate retention charge. The line is not proof a copy can return. Noticing a failed job is support labor.

Support labor is hours times a stated hourly cost. The stated hourly cost on this worksheet is 1000 rupees per hour, a labeled assumption for the multiplication, not a wage survey and not an Adiba rate card. Two hours times 1000 equals 2000. Six hours times 1000 equals 6000. Eighteen hours times 1000 equals 18000. If the real hourly cost differs, change the hours or the envelope.

Contingency is left unassigned so a higher quote, a long restore test, or a request outside the counted hours has a place to land. It is not profit, tax, or a second infrastructure budget. Domain registration, a separate mailbox host, a client-paid theme license, and the agency margin stay off these four lines until someone adds them and redoes the sum. Until that quote work is done, the three figures remain illustrative monthly budget envelopes.

Check each labeled split against the sum

One hourly cost, 1000 rupees, makes the labor cells comparable. The sums below are exact for these labeled assumptions. A different split is valid when the real quote differs.

Envelope	Infrastructure assumption	Backup assumption	Support-labor hours times a stated hourly cost	Contingency	Sum
5000	2200	400	2 hours times 1000 equals 2000	400	2200 plus 400 plus 2000 plus 400 equals 5000
15000	6000	1200	6 hours times 1000 equals 6000	1800	6000 plus 1200 plus 6000 plus 1800 equals 15000
40000	14000	3000	18 hours times 1000 equals 18000	5000	14000 plus 3000 plus 18000 plus 5000 equals 40000

Reading the labor products back into the rows: 2 hours times 1000 equals 2000, so 2200 plus 400 plus 2000 plus 400 equals 5000. Six hours times 1000 equals 6000, so 6000 plus 1200 plus 6000 plus 1800 equals 15000. Eighteen hours times 1000 equals 18000, so 14000 plus 3000 plus 18000 plus 5000 equals 40000.

When a quote moves one cell, rebalance or retire the label. If backup on the middle row is quoted at 2000 rather than 1200, one valid split is infrastructure 5200, backup 2000, 6 hours times 1000 still 6000, and contingency 1800, because 5200 plus 2000 plus 6000 plus 1800 equals 15000. Another leaves infrastructure at 6000, sets backup at 2000, and cuts contingency to 1000, because 6000 plus 2000 plus 6000 plus 1000 equals 15000. If infrastructure on the PKR 5,000 row moves from 2200 to 3500, then 3500 plus 400 plus 2000 plus 400 equals 6300, and the 5000 label no longer fits. If the PKR 40,000 labor cell moves from 18 hours to 24 hours, labor becomes 24000 and 14000 plus 3000 plus 24000 plus 5000 equals 46000.

Keep capacity language off the worksheet

The envelope answers how many rupees are assigned for the month. It does not answer how many sites fit, which panel license is bundled, or how a vendor will act when a site fails. Record the invoice identifier, the service name, and the monthly figure, and test that figure against the infrastructure assumption. A yearly bill contributes only a monthly equivalent the vendor wrote down.

A license fee sits inside one of the four lines or outside the envelope. A license the client buys personally is not an agency infrastructure assumption. The word included, with no fee and no owner, does not fill a cell. Continuity wording stays in the vendor agreement when one is offered. A larger contingency is unused money until a quote or an incident spends it.

Ask the same four questions at every envelope

Before an envelope is described to a client, ask about account ownership, a restore test, who answers the client, and the software versions supported. Ask those questions at PKR 5,000, at PKR 15,000, and at PKR 40,000. Evidence does not become optional on a small envelope, and a capacity claim does not stand in for evidence on a large one. A blank cell means the envelope is not ready to repeat.

Envelope	Account ownership	Restore test	Who answers the client	Software versions supported
5000	Ask which legal name is registrant, panel owner, and billing contact, and whether the agency can export the zone and the account.	Ask for the date a restore finished on a separate copy, who signed it, and which client-visible check was repeated.	Ask who replies to the client, which hours sit inside the 2-hour labor assumption, and which requests sit outside those hours.	Ask which application and runtime versions the vendor will still answer about, written as version strings.
15000	Ask whether a second named person can recover registrar, DNS, and panel access if the first is absent, and where that step is written.	Ask whether the last restore included database and files, and whether the test copy was retired so it cannot be mistaken for the live site.	Ask who replies when the named person is away, and whether those hours sit inside the 6-hour labor assumption or need another quote.	Ask which versions remain in the supported set this month, and what notice arrives before a version leaves that set.
40000	Ask for a written owner on each account this envelope is meant to fund, including who can close an account, without turning the list into a capacity figure.	Ask for a finished restore on the account the client calls most critical, with date, operator, destination copy, and a client-visible check.	Ask which role answers incidents and which role answers ordinary requests, and which of those hours sit inside the 18-hour labor assumption.	Ask for the supported version list of each application in use, and who performs an upgrade when a version leaves that list.

Ownership is the name on the registrar, the panel, and the invoice. A restore test needs a date, an operator, a destination other than the live site, and a client-visible check, with hours taken from labor or contingency. Who answers the client is a person and a finite hour block: two, six, or eighteen. Software versions supported is a list of version strings, not a license entitlement.

A backup job is not a restore

The backup assumption pays for the copy step and for storing copies. Schedule the job, then schedule a restore on hours the sheet already shows, or on contingency when the test sits outside that count. A backup job is not a restore.

The WordPress backup documentation treats copies as site administration: what to include, where copies can live, and why the habit belongs with operating the site. That page does not price these envelopes, and it does not turn 400, 1200, or 3000 rupees of backup assumption into a retention rule. A success line in the job log means the copy step reported completion. When the restore fails, spend contingency, pause changes, or tell the client the backup line still lacks a tested copy. Put the test on the task desk with an owner, a date, and the envelope the hours come from.

Reseller documentation does not set commercial terms

A reseller account may allow further accounts, quotas the upstream host already permits, and contact with that host. Those controls do not set the charge, the budget line, or the envelope.

The WHM reseller documentation explains reseller tools and the limits a parent account can impose. Reseller docs do not set commercial terms. They do not place a feature inside PKR 5,000, PKR 15,000, or PKR 40,000, and they do not set the hourly cost of 1000 rupees. Write a reseller invoice into the infrastructure cell and rebalance. Write a separate backup-storage bill into the backup cell. If host staff answer the agency and not the client, name the agency's own person before that matrix cell is closed. A panel quota is a technical limit, not the envelope. When the quota and the quote disagree, keep the quote and the ownership notes.

Match the next month to invoices and hours

Carry the four assumptions forward only after infrastructure matches invoices, backup matches storage bills, labor matches logged hours times the stated rate, and contingency shows a balance or the line that absorbed it. If actuals were 6300 against a 5000 envelope, the next conversation uses 6300 or a new scope.

The work of agency hosting is the setting for this worksheet. The agency still owes a named owner, restore evidence, a named responder, and a version list. These three envelopes are not current offers. Eighteen hours on the PKR 40,000 row do not also fund the two hours on the PKR 5,000 row unless a shared labor budget names both clients. On a first call the matrix is often blank. A target near PKR 5,000 should seek a scope that can fit near 2200 of infrastructure and two hours. A target of PKR 40,000 should keep a quote that fits 14000 plus 3000 plus 18000 plus 5000, or a written rebalance. The envelope constrains rupees. The vendor's paper decides the scope.

Replace every assumption with a written quote before you promise a client a price.