The practical questions before a B2B project starts.
Scope, ownership, access, agency relationships, production changes and what happens after delivery.
Questions & answers.
Do I need to know what technology I need?
No. A useful first brief can describe the business problem, desired outcome and current environment. The implementation should follow the requirement, not the other way around.
Do you only work with large companies?
No. Project routing is based on what needs to be done, not organisation size.
Do you work with agencies?
Yes. Work can be white-label, low-visibility or directly technical by agreement.
Will you contact an agency's client directly?
Only when the agreed working model requires or permits direct technical contact. The agency's client relationship remains the agency's.
Can you work on an existing website?
Yes, depending on the project. Existing production should be assessed before destructive changes.
Who owns the domain and hosting?
Where practical, the client or agency intended to own them should contract them directly with the provider.
Do I have to send my hosting password?
Preferably not. Delegated access, a limited account or attended remote assistance may be better.
What if I do not know how to give access?
We can provide task-specific instructions when access is actually needed.
Is maintenance included forever?
No. A defined project and ongoing support are separate unless the commercial agreement explicitly says otherwise.
Can the scope change?
Yes. A material new requirement may change price, timing or delivery method and should be identified explicitly.
Do you guarantee rankings, conversions or perfect security?
No. We do not use guarantees we cannot substantiate.
What happens if a third-party provider fails?
We can work within the agreed scope, but external providers remain subject to their own systems, availability and terms.
How do I start?
Use the project brief that best matches your situation. If you are unsure, start with the general project brief.
Still deciding how to start?
Use the general brief. A submitted requirement starts a conversation; it does not automatically create a project commitment.