Listen and define the scope.
We review your business, goal and existing setup. Then we clarify pages, functions, content responsibilities and the project’s boundaries.
PARTNERSHIPS
Complementary expertise. Better-connected projects.
We can explore project-based collaboration with agencies, independent specialists and businesses. Clear roles, deliverables and client communication make it easier to work well together.
COLLABORATION OPTIONS
Let’s define where we can contribute.
A collaboration can cover an entire project or a specific design, content or development requirement. It is important to establish which team is responsible for each part and how the result will be delivered.
- Project-based design and development support
- Complementary expertise for an existing team
- Connected planning for content, brand and web work
- Technical collaboration assessed around the project’s needs
WORKING FRAMEWORK
Clear responsibilities make the process easier.
Client communication, review stages, file sharing and revision scope are discussed at the start. Commercial terms and any confidentiality requirements are agreed for the specific project. No standard commission or referral fee is assumed.
- Clear roles and delivery responsibilities
- The approach to client communication and approvals
- Revisions, timing and commercial terms
- Necessary file access and confidentiality arrangements
PLANPORTS CRM
Consider CRM as part of the business workflow.
Lunea is a certified Planports CRM partner. If you have a CRM need, we can look at your existing customer and operational workflow together. Product choice, licensing, connections and implementation scope are assessed separately; they are not automatically included in a web project.
- Review of current customer tracking and operational needs
- A distinction between web project and CRM scope
- Assessment of licensing and integration requirements
- Progress based on an agreed workflow
STARTING A COLLABORATION
Make the contribution you need specific.
An agency may have a completed design and need development support; an independent specialist may want to add a website alongside their own service. Files, responsibilities and approvals differ in these situations. We first establish where our contribution begins and what output is expected.
Share the current state of the work, intended pages and expected delivery format. If the design is ready, we discuss how fully interactions and mobile behaviour are defined. If content is missing, we agree who prepares it rather than silently passing uncertainty to another team.
The project framework identifies who talks to the client, consolidates revisions and gives final approval. Brand visibility, confidentiality and commercial terms need a separate agreement. The options described here do not automatically create a partnership or referral commission arrangement.
- Existing work and the contribution required
- Source files, content readiness and delivery format
- Ownership of client communication and approval
- Commercial terms to confirm for the specific project
HANDOVER BETWEEN TEAMS
Pass on the decisions, not just the files.
A team receiving screenshots alone may not know which behaviours were approved. Making decisions about menus, form results, language changes and permissions visible helps the next stage. At handover, completed work should be distinguished from information or decisions still outstanding.
A form may look complete while its recipient is still unknown. That should not be handed over as a working form. Test and live environments, along with responsibility for publication, should also be identified separately. Design approval is not an automatic instruction to publish.
Access for joint work is limited to what the task requires. Final delivery, the review checklist and any later support are tied to the project terms. Design, development and client teams can then use the same definition of what is being delivered.
- The current approved design and behaviour
- Completed work separated from outstanding decisions
- Clearly identified test and live environments
- Shared delivery, publication and support responsibilities
How we work
A clear way of working, at every stage.
You know what we are doing, why it matters and what comes next. We define the scope early, keep decisions visible and review the result together before launch.
Shape the structure and design together.
We make the content flow and interface direction tangible. Brand fit, ease of use and priority messages are reviewed together.
Develop and review how it works.
We turn the agreed scope into an implementation, reviewing pages, links and interactions against the project’s use cases.
Prepare for launch with a final review.
We work through the content, technical requirements and delivery scope. Launch and later maintenance follow the agreed terms.
FAQ
Useful answers
As an agency, can we request development support only?
Yes. We can assess collaboration on a specific development task once the technical scope, responsibilities and delivery terms are clear.
Is there a fixed commission for every referral?
No. If that commercial model is relevant, its terms are agreed separately between the parties. This page does not create a commission or payment commitment.
What should we share for a partnership discussion?
Tell us the project goal, current scope, contribution needed and expected delivery format. Do not include customer data or confidential access credentials in the first message.
Let’s Discuss Your Project
Let’s give your next project a clear direction.
A new website, a refresh of an existing platform or software for a specific workflow: tell us what you want to achieve, where you are now and what matters most. We can start the conversation with a practical scope.