This page outlines how collaboration starts, how scope and contracts are confirmed, and how payment is handled. Service-specific scope, pricing, and fit details are covered on each service page. The process applies to:
Scoped services
Ongoing support
See each service page for the details specific to that service.
Send an enquiry and book a call
Share a few short details about your product, target pages or flows, and what you're hoping to address.
Discovery call
A 30-minute call to understand the context, discuss the service, and check whether the scope is a good fit.
NDA confirmation
For scoped services, an NDA is typically required before detailed review and quoting begins. Before an NDA is in place, discussion stays within non-confidential information.
Sola Studio has an NDA template available, and can also review your team's preferred NDA from a confidentiality-scope and operational-fit perspective where appropriate.
Scope confirmation
After the call, scope details are confirmed through a short form or follow-up messages before the quote is prepared.
Proposal and quote
Once the scope and conditions are confirmed, a proposal and quote are shared for review. The engagement is not confirmed until the required contract, payment, and start conditions are completed.
Contract documents
The engagement is documented through an IMSA and SOW. Sola Studio provides templates, and can also review your team's preferred contract format from a service, scope, and operational perspective where appropriate.
Invoice and payment
An invoice is issued and payment is usually handled via Wise. Payment is required before work begins.
Project start
Work begins after the required contract documents, payment, access, materials, and any agreed confidentiality or platform setup are confirmed.
Send an enquiry and book a call
Share a few short details about your current stack, team setup, support needs, and preferred start date.
Introductory call
A 30-minute call to understand your context, discuss the engagement model, and check whether the setup is a good fit.
Scope and terms alignment
After the call, monthly capacity, role, start date, billing cycle, payment method, and any platform requirements are confirmed.
Quote
A quote is shared once the main terms are aligned. The engagement is not confirmed until the required contract, payment, and start conditions are completed.
Contract and NDA
Sola Studio provides contract templates and can also review your team's preferred contract format from a service, scope, and operational perspective where appropriate.
NDA is handled as part of this step where needed.
Billing and payment
Payment method, billing cycle, currency, any upfront or initial payment requirement, and any platform requirements such as Deel are confirmed before the engagement starts.
Engagement start
The engagement starts after contract setup, billing terms, required access, materials, and any required initial payment or platform setup are confirmed.
Payment Method
Payment timing and method are confirmed before work begins
Payment Timing
| Amount | Condition |
|---|---|
| Scoped services — under EUR 5,000 | Full payment upfront |
| Scoped services — EUR 5,000 or above | Full payment upfront by default. Split payment may be available depending on scope and terms. |
| Ongoing support | Monthly billing, confirmed individually |
If new needs come up after the scope, capacity, or terms have been agreed, they can be reviewed separately. Additional pages, flows, implementation review, increased capacity, or follow-up support may require an adjusted quote, updated terms, a separate SOW, or a new engagement.
Sola Studio provides contract templates in an IMSA / SOW format, and can also review your team's preferred contract format where appropriate. Final scope, fees, payment terms, renewal terms where relevant, NDA requirements, and start conditions are confirmed before work begins.
Scoped services
An NDA is typically required before detailed review and quoting begins.
Frontend Partner (ongoing support)
An NDA is handled as part of the contract setup process.
Sola Studio has an NDA template available, and can also review your team's preferred NDA from a confidentiality-scope and operational-fit perspective where appropriate.
Remote by default
Sola Studio works remotely by default. Meetings are usually held via Google Meet or, where appropriate, your team’s preferred video tool.
Structured async collaboration
Sola Studio works across time zones using clear written communication, structured handoffs, and agreed meeting windows. Collaboration is planned around realistic overlap so decisions, next steps, and review context stay visible.
Context, rationale, and documentation
The working style emphasises context, rationale, review notes, and decision records, so implementation and review work can move forward without relying on constant real-time availability.
Existing tools and workflows
Where appropriate, Sola Studio can work with your existing tools and workflows, such as GitHub, Jira, Linear, Slack, Notion, Figma, or Google Workspace, subject to access approval, permission limits, and security requirements.
Access, materials, and timing
Project timing depends on timely access to the necessary materials, accounts, documents, repositories, or review targets. If access or feedback is delayed, the schedule may need to be adjusted.
Tooling and paid accounts
If a paid tool, dedicated account, client environment, or specific platform access is required for the engagement, the setup and any related costs are confirmed before work begins.
Use the enquiry form to share a few details about the service, scope, and timing you have in mind. The next step depends on the type of engagement and what needs to be confirmed first.
Start an enquiry