Your project may be making less money than you think. When job costs aren’t tracked properly, con...Your project may be making less money than you think. When job costs aren’t tracked properly, con...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Hey everyone. I wanted to pick your brains on a freelancing issue I'm facing.
I started working with a client as a subcontractor for Framer development and I got surprised when they told me they have a 30-day window for paying their collaborators.
I never heard about a window that long. For all the client projects I worked on I take a 50/50 approach for payment. Projects start when the 50% downpayment is made, while the remaining 50% is paid upon project completion (I usually set a 10-day window for that).
I can understand having a 30-day window for the final payment, since I'm being subcontracted, but it sounds super weird to me to have a 30-day window for the downpayment. Most small Framer projects are done well before that.
What's your experience so far? Am I being unreasonable? Is this a common practice in the industry?
An automation quote needs three budgets—not one headline price.
Before approving a pilot, separate:
BUILD: the agreed workflow, integrations, data preparation and acceptance tests. Write down what is outside the first scope.
RUN: hosting, software seats, messages and AI/API usage where applicable. Record who pays each provider and what usage assumption the estimate depends on.
MAINTAIN: monitoring, fixes and future changes. Specify what support includes rather than assuming every new requirement is covered.
Ask one useful question: “What changes in the monthly bill if our volume doubles?”
You may not know the answer precisely before a pilot. Mark it as an estimate, measure actual usage and revisit it before expanding. Agree who receives cost alerts and what happens if a spending threshold is reached; confirm which controls the chosen tools actually support.
A small first workflow can make the uncertainty easier to measure. It does not make ongoing costs disappear.
ROVELK builds scoped business automations. Message me with the repetitive task, tools involved and approximate weekly volume—no customer records needed. We agree scope, price and external costs before work. Project discussions: Russian / Ukrainian.