Stop losing money on Make Automation Specialist projects.
Send your first 3 upfront payment contracts for free. Building complex Make.com active scenarios, mapping JSON arrays, and configuring custom webhooks requires deep technical expertise—yet too many automation specialists start building before securing their deposit, only to get stuck in API credential limbo or hit with unfair chargebacks when a client's third-party app changes its payload.
No credit card required. Setup takes 30 seconds.
Build the agreement, add your deposit amount, and send one secure client link for signature and payment.
Statement of Work
Ref: 2026-001 • Standard Business Template
Scope of Work
The Make Automation Specialist (the "Specialist") will design, configure, and test workflow automation scenarios using the Make.com platform as specified in the agreed-upon project brief. The scope is strictly limited to mapping the specific endpoints, webhooks, and data routers detailed in the deliverable schedule. Any modification to third-party APIs, database schemas, or payload structures by the Client during the project is considered out-of-scope and will require a separate upfront fee.
Upfront Payment
The Client agrees to pay 100% of the project fee upfront (or the designated initial milestone deposit) using the MicroFreelanceHub secure payment link. No work, workspace configuration, API credential collection, or workflow architecture design will commence until this payment is processed and cleared. This upfront payment is non-refundable and secures the Specialist’s development bandwidth.
Client Review
All scenario testing and initial execution runs will be hosted in the Specialist's developer workspace. The Specialist will demonstrate the functionality of the automated workflows via recorded video or live screenshare using mock or sandboxed data. The Client is responsible for reviewing the data mapping, webhook triggers, and conditional logic filters during this review period.
Approval Deadlines
Upon notification that a workflow scenario is ready for review, the Client must approve or provide consolidated feedback within forty-eight (48) hours. If the Client fails to respond within this timeframe, the workflow will be deemed approved, and the milestone will be marked as complete. This prevents project stagnation and ensures predictable deployment schedules.
Delivery Conditions
The transfer of workflow ownership (including migrating Make.com blueprint JSON files, activating active webhook URLs, and connecting live production API keys) will occur only after all payments are fully cleared through MicroFreelanceHub. The Specialist retains full intellectual property rights to the scenario design and custom script logic until the final approval record is locked and payment is received.
Refund Limits
Due to the custom nature of software automation and API integration, no refunds will be issued once development has commenced. In the event that a third-party platform changes its API access, deprecates endpoints, or experiences downtime during the project lifecycle, the Specialist is not liable, and no refunds or discounts will be provided for issues stemming from external application failures.
Termination
Either party may terminate this agreement with written notice if the other party breaches these terms. If the Client terminates the contract for convenience before project completion, any upfront payments or milestone deposits paid to date are forfeited to the Specialist as liquidation damages for reserved development time.
API and Webhook Dependency Changes
Clients may change their third-party API configurations or revoke credentials mid-project, causing scenarios to fail. Without upfront payment, you bear the financial risk of diagnosing external system failures.
Workspace Hostage and IP Theft
If you build inside a client's Make workspace without prior payment, they can revoke your access, clone your complex mapping patterns, and refuse to pay for your architecture.
Operation Runaway and Overages
Testing custom loops and iterators can rapidly consume Make operations. If a client delays approval while the scenario runs live, you may face unexpected platform billing costs without upfront security.
What is a Make Automation Specialist Upfront Payment Contract?
To secure upfront payments, Make Specialists must require cleared payment via MicroFreelanceHub before accessing client API credentials or building scenarios. Define strict project milestones, implement a 48-hour feedback deadline, and retain blueprint ownership in your developer workspace until the client approves the test runs and pays.
Built from real freelance projects
This template is based on real-world scenarios across freelance projects where unclear scope, missing payment terms, and revision creep led to lost revenue. It is designed to protect your time, define expectations, and ensure you get paid.
Why Make Automation Specialists need a clear upfront payment contract
In the world of workflow automation, the line between setup, testing, and deployment is incredibly thin. Once a Make (formerly Integromat) specialist configures a scenario, connects the client's API keys, and routes live data, the value has been fully delivered. If you work on net-30 terms or wait until final approval to request payment, a client can easily copy your logic, duplicate the scenario to their own team workspace, and ghost your invoices. Upfront payment protection is not just a financial preference; it is a technical necessity. By requiring a cleared upfront payment before configuring any webhooks or mapping routers, you protect your proprietary logic. MicroFreelanceHub enables you to lock in these funds alongside signed contract terms, ensuring that your specialized knowledge is valued and protected before you consume your execution operations or run live tests on your own billing plan.
Real-world scenario
Consider Alex, a Make Automation Specialist hired to sync a client's HubSpot CRM with an Airtable database and Slack via complex webhook filters. Alex spent ten hours mapping nested JSON arrays and building custom filters. Because he didn't secure an upfront payment, he built the scenarios directly in the client's Make workspace using their active API keys. Once the integration worked flawlessly, the client quietly duplicated the scenario, deleted Alex's user profile from the workspace, and ignored his invoice, claiming the integration 'took too long to set up.' If Alex had used MicroFreelanceHub, he would have secured a 100% upfront deposit before starting, kept the scenario in his own developer workspace for testing, and only transferred ownership after the integrated approval record and payment link were fully resolved. The client would have paid first, and Alex's intellectual property would have remained safe.
🛡️ What this upfront payment contract covers:
- ✓Make.com Scenario Blueprint JSON files
- ✓API endpoint mapping and webhook routing configuration
- ✓Integromat/Make active path error-handling routers
- ✓14-day execution log monitoring and optimization report
Best practices for Make Automation Specialists
Keep Blueprints Local Until Paid
Always build, test, and run scenarios inside your own developer Make account first. Only import the blueprint JSON to the client's workspace once upfront payment is secured.
Use MicroFreelanceHub Approved Milestones
Tie your payments to clear, objective system triggers (e.g., 'Successful test webhook run with 200 OK response') rather than subjective client satisfaction queries to avoid endless scope creep.
Legal Disclaimer: MicroFreelanceHub is a software workflow tool, not a law firm. The templates and information provided on this website are for general informational purposes only and do not constitute legal advice.
Frequently Asked Questions
Can I stop work if a client delays sending their API credentials?
Yes. This contract states that the project timeline pauses immediately if API credentials or required third-party access are not provided within 3 business days of the upfront payment clearing, protecting you from artificial delays.
How does this contract prevent clients from filing credit card chargebacks?
The contract includes an explicit waiver of chargeback rights once a '200 OK' API response or a successful test run is documented. MicroFreelanceHub's digital signature and approval workflow provide undeniable proof of delivery to payment processors.