Frequently asked questions

The client goal, the scope of work, the agreed deliverables and the criteria that count as done. You build the phases or sprints straight from the brief, and every deliverable gets an owner, an hours estimate and a due date.

The client gets the deliverable in one dedicated place, leaves feedback on it and approves it explicitly. The sign-off is stored with a date and an author, and the feedback stays attached to the version it refers to.

You flag them as out of scope and they go to quoting instead of being done quietly. An extra revision round becomes a new line in the quote or a decision you own, not a loss you find on the invoice.

Every deliverable compares estimated hours against tracked hours, and the project shows how much of the budget is gone versus how much is left to deliver. When that ratio breaks, you can see exactly which phase blew the estimate.

No. It is not a design or development tool — Figma, Git and your IDE stay where they are, and the sites themselves get built elsewhere, for example with 4buildsite.net. 4webagency owns the coordination, the deadlines, the hours and the money.

Billing details, contacts, the contract, past projects, the current retainer and the domains or hosting you manage for them. It is not a full sales CRM with prospecting automation — the commercial pipeline lives on 4softcrm.net.

A retainer has included hours per month and a balance that resets each cycle; a fixed-fee project has one total hour budget until delivery. Both are tracked the same way, but reported differently.

You get an alert before you cross the limit, not after. Overage hours are flagged separately and can be billed at the agreed rate or carried over, depending on the contract.

The platform compares what you invoiced a client with the hours tracked against them at role-based rates. Example: a 4,000 RON retainer for 20 hours that burns 26 hours drops your real rate from 200 to 154 RON/hour — visible in the month it happens.

Yes. The monthly report shows deliverables handed over, hours used against hours included, and the status of the domains or hosting you manage. Export it and send it as an annex to the invoice.

Every domain, hosting package and SSL certificate you administer, grouped by client, with expiry date, cost price and rebilled price. One list instead of a spreadsheet plus four provider panels.

Every record carries an expiry date and alerts the owner inside the agency days ahead of the deadline. If a domain does lapse, the client site and email go down, and recovery runs through the registrar grace period and costs more than renewing on time.

Yes. Cost price is kept separate from the client price, so the management margin is visible on every line. Example: 40 .ro domains renewed yearly and rebilled with a 15% management fee.

No. 4webagency is not a registrar: it manages the portfolio, the deadlines and the rebilling, but registration and payment stay with your registrar or hosting provider. For hosting and VPS inside the ecosystem there is 4hosting.net.

You log time against a project and a deliverable, marking hours billable or non-billable, with a rate per role. At month end you push only the billable hours, at their rates, and the timesheet stands as the supporting document for the hours billed. Payroll and leave stay with 4softhr.net and 4mystaff.net.

Invoicing runs through 4invoices.net, which covers the mandatory RO e-Factura B2B regime (OUG 120/2021 and Law 296/2023). Bookkeeping itself stays with 4conta.ro; 4webagency supplies the hours and the invoice lines.

Four plans — webagency-start, webagency-plus, webagency-pro and webagency-premium — chosen by number of users and active projects; the full grid is on the pricing page. During setup we import clients, live projects and the domain portfolio from CSV or Excel, so you can track time in the first week.

Your client data and the credentials you hold for their domains and hosting belong to the agency and can be exported at any time. This is ordinary personal and business data under GDPR (Regulation EU 2016/679), protected with encryption, role-based access and an audit log, and we act as data processor. Reach us on /contact or [email protected].