PTR Golf Platform Engagement

The following transfers to PTR Golf on completion of Phase 5.

Twelve weeks from kickoff. Weeks 1–10 are development; weeks 11–12 are the acceptance programme described in Phase 5. Three things run on this calendar and all three have to hold for the date to hold: the build, the acceptance gates that release payment, and what PTR Golf supplies. The third is the one that most often moves a date, so it is shown here rather than left in the phase notes.

The advance is invoiced on signing and shown at the head of the chart, where it lands. It carries the Phase 1 block, which is why the week 2 gate raises no further invoice — Phases 1 and 2 are then billed together at week 4. Every other gate is invoiced on acceptance.

Two deliverables are scheduled ahead of their phase group. The Founding Member campaign is live in week 2. The Admin CMS is delivered in week 4, giving PTR staff content control for eight weeks before launch.

Two dependencies decide whether twelve weeks holds, and both should be started in week 1 even though they are not needed until later. The data exports from x4Golf and fringegolfers are not due until week 8, but they are requested from third parties who have no obligation to hurry — that request should go out on day one. The live payment-processor account is not needed until week 5, but underwriting and business verification can take several working days and cannot be rushed once started. Everything else on the list is content PTR already owns.

Each gate is accepted against the written exit criteria set out in its phase above, not against opinion. Where an item PTR owes arrives late, the affected phase and every phase after it move by the same period, as set out under Payment terms — the schedule extends by the period of the delay. Nothing is invoiced for a gate that has not been accepted.

Fixed price. The figure below covers the 36 deliverables and does not move unless scope changes under the change-control terms above.

₹1,00,000 — one eighth of the fee — is held back to final handover, and falls due only when Phase 5 is accepted: onboarding complete, hardening and UAT signed off, the platform live, and source code, infrastructure and administrator access transferred to PTR Golf. Nothing about that transfer is conditional on the payment — ownership vests on creation under the intellectual property terms — but the retention means the final invoice and the finished platform arrive together.

There are five payments against five phases, not six: Phase 1 acceptance in week 2 releases no invoice, because the advance already covers it. Phases 1 and 2 are then billed together at the week 4 gate. The figure shown against each phase above is what that phase is worth; the table here is when it is invoiced. Invoices are due within 14 days of acceptance, and work on the following phase continues during that window.

• Currency Fees are quoted and invoiced in Indian rupees and payable by bank transfer. Where PTR Golf elects to pay in US dollars, the amount is converted at the telegraphic transfer selling rate on the invoice date. Bank charges levied outside India are to PTR Golf's account.
• Tax No Indian GST is charged on this engagement. The supplier is not registered for GST in India, and payment originating from the United States constitutes an export of services falling outside the scope of Indian GST. Should payment instead originate from within India, or should the supplier become liable to register for GST during the engagement, GST at the prevailing rate — currently 18% — would be added to invoices issued from that date forward. Invoices already raised and settled are unaffected. Any taxes, duties or withholdings imposed outside India are to PTR Golf's account.
• Payment terms Invoices fall due 14 days after phase acceptance. Amounts outstanding beyond 30 days carry interest at 1.5% per month. Where an invoice remains unpaid 30 days after its due date, work on subsequent phases may be suspended on four days' written notice, and the schedule extends by the period of suspension.
• Termination Either party may terminate this engagement on 14 days' written notice. On termination PTR Golf pays for every accepted phase in full, plus work completed on the phase in progress on a pro-rata basis against its deliverables. The supplier delivers all work product completed to that date, in the same form as the Phase 5 handover.
• Intellectual property Ownership of all code, designs and data vests in PTR Golf on creation, as set out under Security, compliance and data ownership. This is not conditional on payment, and it survives termination.
• Liability The supplier's aggregate liability under this engagement is limited to the total fees paid. Neither party is liable for indirect, incidental or consequential loss, including loss of profit, revenue or anticipated savings. Nothing limits liability for fraud or wilful misconduct.
• Third-party services Cloud and third-party service fees are contracted directly between PTR Golf and each provider. The supplier configures and operates those services but is not a party to their terms and carries no liability for their pricing changes, outages or discontinuation.
• Validity This statement of work is open for acceptance for 30 days from the issue date shown below. Hosting costs and third-party pricing are re-confirmed at signing.

Built on PERN — Postgres, Express, React, Node. The application runs on Amazon Lightsail, platform data sits in Amazon RDS for PostgreSQL, media in Amazon S3, and the front end, DNS and CDN on Cloudflare. Every account is opened in PTR Golf's name and billed directly to PTR at cost, with no markup.

Infrastructure is sized against three load profiles. The platform is built to full high availability and ships at launch with parts of it switched off, because at launch there is nothing yet to lose. Redundancy is added as the business earns it — each step is a console change on infrastructure already designed for it, not a rebuild, and each has a published trigger and a known price in the ladder below.

The savings against a conventional EC2 build are stated per line. Each card also says plainly what PTR gives up in return, so the trade is visible rather than buried in an instance size.

Each tier is sized so that peak load consumes approximately 60% of available capacity, leaving 40% headroom. The load test at the Phase 4 gate verifies this against the contracted target. On the Launch tier, 300 concurrent users on an ordinary evening consume roughly 15% of the application server and 20% of the database — the tier is not near its limit at the load PTR expects to carry daily, and does not need changing on traffic grounds until sustained concurrency approaches 800.

Sizing is a planning allowance, confirmed through testing at the Phase 4 gate. Growth adds a worker and a load balancer; Expanded adds two workers. US East pricing assumed. S3 requests and media downloads, transfer above the bundled Lightsail allowance, domain renewal and payment-processing fees are extra. Maintenance is separate and is set out in the next section.

The Launch tier is not a stripped build that must one day be replaced — it is the full architecture with its redundancy switched off. Each line below is a console change on infrastructure already provisioned for it, made in an afternoon with no downtime and no code change. PTR is told the trigger in advance and sees it coming on the monitoring dashboard, so nothing here arrives as a surprise on an invoice.

Taken together, the load-driven steps are what turns the Launch tier into the Growth tier. On the growth assumed here, the first is reached in month 12–18 and the bill sits between ₹9,000 and ₹13,000 a month for the whole of year one. What moves the number first is data and email volume, not visitors — at 100–300 concurrent users a day, traffic is not the constraint on this tier and will not be for some time.

Stripe sits outside this table: no monthly fee, 2.9% + $0.30 per transaction deducted from takings. The domain is provided and renewed by PTR Golf. Tournament SMS, if added later, runs about $0.008 per message. Figures are USD at published rates for US East, verified on 11 September 2026 against AWS, Cloudflare, Clerk and Resend published pricing. Rupee equivalents are converted at ₹95 to the dollar, the rate on the same date. Both the exchange rate and provider pricing should be re-confirmed at signing; infrastructure is billed to PTR in dollars regardless.

The retainer begins when the 30-day warranty period ends. Either party may terminate it with 30 days' written notice; exit assistance applies regardless.

Most of a maintenance retainer is not new work. It is the cost of a platform being looked after in a month when nothing is asked of it and nothing goes wrong — which, done properly, is most months. The table below is what happens on the platform every month whether or not PTR sends a single request.

Both tiers work out at roughly ₹1,750 an hour, which is the retainer rate rather than the project rate. The difference between them is not mainly hours: Priority buys 24×7 cover on critical incidents, which is what a tournament weekend actually requires, plus the annual Singh Open and PGL rollover and a change freeze around live events. Unused change hours do not roll over. A month needing more than its allowance is quoted before the work starts, never billed after it.

Work outside the retainer is charged at ₹2,200 an hour, or quoted as a fixed price before it starts, whichever PTR prefers. The retainer rate is lower than the hourly rate deliberately — that gap is what the commitment buys.

Recovery objectives at every tier: a recovery point of 5 minutes, using point-in-time recovery across a seven-day window. Recovery time differs by what is switched on. On the Launch tier, a failed application server is restored from its most recent Lightsail snapshot, and a database failure is a restore of about 30 minutes. Once Multi-AZ is on, database failover between availability zones is automatic and completes in 60–120 seconds, with one hour as the outer bound for a full restore from snapshot. The availability targets above follow directly from this and are the reason the Launch figure is stated at 99.5%: Amazon publishes 99.5% for a Single-AZ database and 99.95% for Multi-AZ, and PTR should not be promised a number its infrastructure cannot support.

Controls applied to member records, payment relationships and published results.

Risks to delivery, with the mitigation applied to each. The register is reviewed and updated at every phase gate.

Signature by both parties constitutes acceptance of the 36 deliverables, the phase gates, the fee and payment schedule, and the commercial terms set out above.

The named decision-maker required under Governance should be recorded at signing, together with the project sponsor on each side for escalation purposes.