odd little bits.Your agency has a website or web app to deliver, but not the development capacity for this particular job. Odd Little Bits can take on the agreed build behind your agency's brand, while you remain the client-facing contact.
We work fully online, with scope, questions and progress handled in writing. You keep the client relationship and final approval; we agree the development work and handover with you before the build starts.
Get in touchWhite-label does not mean handing over a brief and hoping for the best. Agree who makes decisions, who gathers client feedback and what the client will see of the development process.
Your agency can lead the client relationship, supply designs and content, and consolidate approvals. Odd Little Bits can scope and build the agreed development work, share work for your review and hand over the source and setup notes. The exact split depends on the project.
Discuss confidentiality, client contact and the use of your brand before any work is shared. If a client needs a technical explanation directly, decide whether and how that happens rather than assuming the developer will contact them. Agree how previews, documentation and handover will be presented under your agency's brand. Specific terms belong in the project agreement, not in a blanket promise on this page.
Connections to a CRM or another business tool may form part of a project. If information needs to move between systems, the integration work is scoped alongside the build, not promised merely because the tools have names.
These are possible kinds of work, not examples of past client projects or a fixed list of platforms. What is feasible depends on the designs, existing system and access available.
A useful first brief tells us what your agency has promised the client and what is ready now. Include the pages or features, approved designs, supplied content, existing code or system, and any fixed platform requirements. Point out what is still awaiting a client decision.
Then agree the working arrangement:
We work through the scope, deliverables, budget and boundaries in writing. A date or cost cannot be confirmed from the words “build the supplied designs” alone. Our development brief for agency projects helps put the wider project in one place; the design handover checklist covers approved versions, responsive behaviour and missing states.
This example is invented to show the decisions involved, not a client engagement or a standard package.
A small agency has approved desktop and mobile designs for a service website. It owns the client conversation and will supply final copy. Odd Little Bits is asked to build the pages and an enquiry form. The form's destination and confirmation behaviour are still undecided, so those parts cannot be quoted as a known working connection.
The agency consolidates client feedback into one written list. We share a working version for review and check the agreed layouts, navigation and form states. Before acceptance, the agency confirms the form's actual delivery route and who will test it. A preview that looks right does not prove enquiries reach their destination.
The handover includes the source, setup notes and any remaining decisions. Who publishes the site and who supports it afterward are agreed separately. The client sees the presentation and contact route the agency has approved.
Your agency reviews work against the agreed scope and takes the final client decision. If feedback changes the brief, we agree the effect on work and timing before treating it as part of the build. A defect against an agreed behaviour is different from a new request.
At handover, the source, configuration notes, access arrangements and known follow-up work should be clear. Ongoing monitoring or maintenance is not assumed; it can be scoped separately if needed. See how the wider project process works.
Send an outline of the project, which designs and content are ready, the existing tools involved and any deadline. Tell us how your agency wants client communication, review and handover to work. You do not need to share passwords, access tokens or confidential customer records in an initial brief.
Get in touchOpens the contact form on Tally in a new tab.