Client projects and deliverables

Where service projects go wrong

A web agency in Pune agrees a build over a phone call and a short email. Three weeks in, the client sends fifteen change requests on WhatsApp, each small, each reasonable. No one records them, the team absorbs the work, and the final invoice is for the original amount. The project finishes late, the margin disappears, and the client believes everything was in scope from the start.

The remedy is not a more elaborate tool but a short chain of records: an agreement that defines scope, a task list that mirrors it, and a rule that anything outside scope is written down and priced before it begins.

Estimates add another layer of risk. Teams quote in days from memory, then discover that testing, client review cycles and waiting for assets consumed as much time as building. Compare estimates against actual hours at the end of every project and use the ratio, perhaps one and a half times the first guess, to correct the next quote.

Writing scope so that it can be checked

A scope statement works when a third person could read it and tell whether a request falls inside. List the deliverables by name, describe what done means for each, set the number of revision rounds included, name what the client must supply and by when, and state what is excluded. For an app build, that means screens, platforms, integrations and hosting separated into lines.

Indian service contracts also benefit from a clear payment schedule and a governing-law clause. For work with a foreign client, add the currency and the place of arbitration, and take advice on the wording from a lawyer, since drafting choices here decide who bears the risk.

Include an acceptance clause: the client has a fixed number of working days to test a deliverable and report defects, after which it is deemed accepted. Without it, delivery can hang in review for weeks while the invoice waits.

Tasks, deliverables and deadlines in 4myprojects

In 4myprojects a client project holds tasks, owners, due dates and deliverables. Mirror the scope list: one deliverable per line of the agreement, with tasks beneath it. When a client asks for something new, create a task labelled as a change request so that it is visible and countable, and do not start it until the client approves the price and the time impact.

The project view also answers the weekly question the client asks: what is done, what is late and what do you need from us. Sharing a status that is generated from the task list is less work than writing an update from memory.

Dependencies deserve a field of their own. Many delays come from the client: content not delivered, approvals pending, access credentials missing. Mark such tasks as waiting on the client with a date, and mention them in the weekly status. When the final deadline slips for those reasons, the record shows whose delay it was and the agreement can allow a matching extension.

Agreeing and signing changes

Treat a change request like a small contract. Describe the change, the extra cost and the new date, send it through approval in 4mycontracts and collect an electronic signature from the client. Electronic signatures are valid under the Information Technology Act, 2000, though certain documents need stamping depending on the state and the instrument, so ask your lawyer which of yours do.

The result is a folder in which the original agreement and each signed change sit together. When a dispute arises at the end, the argument is about numbers on documents both parties signed.

Billing at milestones with 4invoices

A common structure for Indian project work is a payment tied to milestones, for example 30 per cent on signing, 40 per cent on delivery of the first release and 30 per cent on acceptance. On a ₹6,00,000 project that is ₹1,80,000, ₹2,40,000 and ₹1,80,000, each plus GST at the applicable rate.

Issue the invoice from 4invoices the day the milestone is accepted, with the project name and milestone in the description, and keep the PDF in the archive. Late invoices are the typical reason that a firm that is busy is still short of cash.

Do not forget GST on the invoice: IT and design services are taxable, the rate applies on the taxable value, and services supplied to a client abroad may qualify as export of services subject to conditions. Whether a particular project does so is for your accountant to confirm before the first invoice goes out.

Closing a project properly

At the end, hold a short review with the team: planned versus actual hours, number of change requests, margin on the project and one lesson for the next quote. Archive the final deliverables, the acceptance note and the last invoice together. A project that is closed on paper is a project you can quote again with real data.

None of these tools replaces judgement on pricing or legal terms, and 4b2b does not file anything with any authority; they make the evidence of what was agreed, built and billed easy to find.

Keep one internal rule for credit: a project is closed only when the last invoice has been paid, not when the work is delivered. Reviewing outstanding invoices by project every Monday catches the slow payers early, and the aged list shows which clients should pay an advance next time.

Define the scope in a signed agreement, state the number of revision rounds included and require a written, priced change request for anything outside it. Record every request as a task in your project tool. Clients accept limits more readily when the process is explained at the start than when it is introduced halfway through.

Many Indian agencies take an advance on signing and then bill at defined milestones, so payment follows delivery without long gaps. The right split depends on risk, project length and client size. Put the schedule and the GST treatment in the agreement, and ask your accountant to confirm the tax side. The advance also screens out clients who are not serious before the team starts work.

Electronic records and signatures are recognised under the Information Technology Act, 2000, and many commercial agreements are signed this way. Some instruments may still require stamp duty payment, which differs by state, or other formalities. Confirm with your lawyer for each document type before you rely on an electronic signature alone. Ask your lawyer about the stamp duty position for your state and instrument.

4myprojects holds tasks, deliverables, owners and deadlines for client projects. Use it to see what is late and what is waiting on the client. Profitability, such as comparing hours with price, you calculate from the task data and the invoice amounts, since the app does not run accounting. Tracking hours is simple to add by comparing task dates with your own timesheets.

Deliver and get paid

Link projects, contracts and invoices.