BUSINESS & AGENCY SERVICES
DeshTech works with businesses and agencies in Sri Lanka and internationally on website delivery, business email and technical decisions. This service group brings together white-label web development, business email setup and technical consulting.
An agency may need help delivering work under its own client relationship. A business may need a professional email setup or a clearer assessment of a technical proposal. Start with the result you need, the people involved and the responsibilities that must remain with your team.
CHOOSE THE RIGHT ENGAGEMENT
Discuss a defined website project, development task or delivery phase. Clarify whether DeshTech communicates only with the agency or participates in approved client discussions.
Identify your domain, current mail provider, users and required devices. Separate new-account setup from mailbox migration, productivity tools and ongoing support.
Bring the problem, current systems, proposals and constraints. A useful consulting scope defines the questions to answer and the written output that supports the decision.
Review which accounts, files, licences and documents your team needs to operate the delivered work. Establish what can be transferred and what remains governed by third-party terms.
SERVICE AREAS
Discuss website development delivered within an agency’s client relationship. Define the brief, technology, review process and acceptance requirements before work begins. Brand presentation, client contact, confidentiality, portfolio use and account access should be agreed explicitly. The arrangement needs clear responsibility for content, feedback and final approval.
Explore White-Label Web DevelopmentPlan business email on your own domain, including the chosen provider, user accounts and domain configuration. The scope may include mailbox migration, aliases, shared addresses and device setup, depending on the platform. Agree who administers the service and what support is needed after setup. Email authentication work should match the actual sending systems.
Explore Business Email SetupAssess a website, system proposal, migration or technical delivery concern with a defined set of questions. The engagement should identify what can be reviewed from the available access and evidence. Outputs may include findings, options, risks and a prioritised action plan. Implementation is a separate scope unless it is included explicitly.
Explore Technical ConsultingAGENCY COLLABORATION
Share the agreed customer requirements, design inputs, content responsibilities and deadlines. Identify assumptions and acceptance criteria so both teams understand what the delivery covers.
Name the agency contact and technical delivery contact. Agree review channels, meeting participation and who can approve changes. Direct client communication should follow the agency’s authorised arrangement.
Plan how designs, functionality and content are reviewed. Consolidated feedback and recorded decisions help distinguish corrections from new requirements. Additional scope needs an approval route.
Confirm the accounts, files, documentation and editing guidance to be delivered. Agree who supports the customer after launch and how new requests or defects are reported.
CONFIDENTIALITY & OWNERSHIP
White-label delivery needs more than removing a developer’s name from a website. Agree which brand appears in communications, whether client contact is permitted and how project information may be used. Any confidentiality or non-disclosure terms should be established for the actual engagement.
Code, design files, content and account access can have different ownership and licence conditions. A third-party theme, plugin, font or hosted platform may carry restrictions or recurring fees. Identify these dependencies before treating every element as freely transferable.
Portfolio permission is separate from project delivery. An agency relationship should state whether the work can be named, shown anonymously or kept confidential. Agree the publishing scope before sharing client work publicly.
BUSINESS EMAIL
For a new email service, confirm domain control, the chosen provider and the accounts your team needs. Decide which addresses belong to individuals and which represent shared business functions. Account recovery and administrator access should remain clear.
For a migration, assess the mailboxes, existing records and other services that send on your domain’s behalf. Website forms, invoicing tools and marketing platforms may need configuration alongside staff email. The transition plan should explain what moves, what remains and when settings change.
Domain authentication can help receiving systems assess authorised mail, but no setup can guarantee that every message reaches an inbox. Provider rules, sending behaviour and recipient systems also affect delivery. Ongoing administration and troubleshooting should be agreed separately where required.
CONSULTING OUTPUTS
Frame the decision clearly: improve or rebuild a website, choose between approaches, understand migration risks or clarify a supplier proposal. A broad request to review everything rarely provides a useful boundary.
Record the access, documentation and examples available for review. Distinguish observed findings from assumptions and areas that could not be inspected. A limited review should not be described as a full certification.
Compare approaches against the business constraints, operational needs and available resources. Identify dependencies and trade-offs rather than recommending a platform before understanding the requirements.
Describe the actions, owners and information needed to proceed. Separate urgent fixes from later improvements. Where implementation is proposed, define its scope and responsibilities before it becomes delivery work.
ILLUSTRATIVE ENGAGEMENTS
The following are generated examples for discussion. They are not completed client case studies or evidence of measured results.
An agency supplies approved designs and content for a business website. The delivery brief defines page types, forms, integrations, review stages and how the agency will receive the completed work. The client-contact and portfolio rules are agreed before access is granted.
A business wants domain-based mail for its team and needs to retain existing messages. Discovery would confirm the old and new providers, mailbox sizes, user access, domain records and a suitable transition plan.
A business has received a proposal to replace an existing website. A consulting brief could assess the stated problem, retained content, integration dependencies, ownership terms and migration requirements before a delivery decision is made.
SCOPE & COMMERCIAL TERMS
For agency work, the design and content readiness, feature requirements, review arrangements and handover scope affect the estimate. Clarify how changes are approved and whether recurring capacity or a single project is being discussed.
For email work, user numbers, mailbox sizes, provider compatibility, domain access and support needs affect the engagement. Platform subscriptions and renewals should be distinguished from setup or migration services.
For consulting, agree the questions, access, investigation boundary and expected output. An assessment can recommend implementation without including it in the same fee. No fixed turnaround, unlimited revisions or response commitment is assumed without an agreed scope.
WORK WITH DESHTECH
DeshTech began in 2017, registered as a business in 2019 and incorporated as a private limited company in 2025. Its website portfolio includes Sri Lankan and international work. Explore those examples and discuss the contribution most relevant to your requirements.
For a new engagement, agree who makes decisions, how feedback is collected and which accounts the delivery team can access. These practical details support a clearer working relationship across businesses, agencies and locations.
COMMON QUESTIONS
Discuss the arrangement at the start. Client communication, branding, confidentiality, portfolio use and support responsibilities need to be agreed for the engagement. A white-label arrangement should be explicit rather than assumed.
Only under the agreed communication arrangement. Define the agency contact, permitted client interaction and approval process before delivery begins.
A clearly defined development task or delivery phase can be discussed. Share the existing work, platform, access and acceptance requirements so dependencies and handover can be assessed.
No. Email setup and website development are different scopes. A website enquiry form may also depend on email configuration, so identify that connection if both services are involved.
Only when implementation is expressly included. A consulting engagement should define the review and its outputs; development, migration or ongoing support can then be scoped separately.
Share the project goal, current website or provider, available brief and intended timing. Redact private customer information. Do not send passwords, mailbox exports or confidential client material through a general enquiry form.
NEXT STEP
Share whether you are an agency or a direct business client, the technical work you need and who will manage approvals. We can discuss a delivery, email or consulting scope with responsibilities that fit your organisation.