SOFTWARE, AI & AUTOMATION
DeshTech helps businesses in Sri Lanka and internationally scope software, automation and connected workflows around the way their teams work. Start with the task you need to improve: organising information, handling requests, connecting systems or helping staff find the right answer.
Our service areas include custom application development, AI agent development, business process automation and system integration. The appropriate approach depends on the workflow, available data, existing systems and the level of control your organisation needs. We assess feasibility and agree the delivery scope before committing to a particular technology.
FIND THE RIGHT APPROACH
A shared application may help when people need consistent records, defined roles and a clearer process for updating information. First identify which records are authoritative and who should be able to change them.
A rules-based workflow may be enough for predictable steps such as moving approved data between systems or routing a request. AI is considered only where interpretation or language handling adds useful value.
An integration assessment checks whether the systems provide supported interfaces, what data can be exchanged and how updates, failures and permissions should be handled.
An AI-assisted tool may help with searching approved material or preparing a first draft. Its access, sources, review requirements and limits should be explicit.
SERVICE AREAS
Plan a business application around actual users, records and decisions. The scope may include role-based access, structured data entry, dashboards and connections to existing tools. Begin with a small set of essential workflows so acceptance can be defined clearly. Migration, hosting, documentation and ongoing support need separate ownership decisions.
Explore Custom Application DevelopmentAssess an AI-assisted workflow with defined tasks, approved information sources and clear tool permissions. A useful starting point is a narrow pilot with examples of acceptable and unacceptable outputs. Human approval, evaluation, operating costs and failure handling should be designed before expanding access or allowing consequential actions.
Explore AI Agent DevelopmentMap a repeated process and identify which steps can follow reliable rules. A scope can cover triggers, approvals, notifications, data transfers and exception handling. Automation should leave a trace of what happened and provide a practical way for staff to intervene when a step cannot be completed.
Explore Business Process AutomationAssess the exchange of information between applications using supported APIs or other agreed interfaces. Define the source of truth, field mapping, update direction, authentication and error handling. Third-party API availability, rate limits and subscriptions influence what can be delivered.
Explore System IntegrationILLUSTRATIVE WORKFLOWS
These are generated examples for discussion, not claims about completed DeshTech client projects. Each would need discovery, system access and a separate feasibility assessment.
A submitted request enters a shared queue, moves to a designated reviewer and creates a notification after a decision. The design needs to explain who can approve, what happens when information is missing and how the decision is recorded.
Staff ask questions against an approved document collection. The assistant returns relevant source references or says when it cannot find sufficient information. Access should follow document permissions, with human review before answers are used for important decisions.
A confirmed record in one application creates or updates a record in another. The workflow needs duplicate checks, a record of failures and a way to retry safely without creating the same item twice.
DELIVERY PROCESS
Identify the people, systems, inputs and outputs involved. Record exceptions and manual workarounds as well as the usual path. Agree which problem matters most and which baseline information is available.
Prioritise a small set of outcomes, users and data flows. Confirm requirements, dependencies, operating costs and acceptance examples. Document which ideas are deferred so the first release has a manageable scope.
Use agreed examples to review workflow behaviour, permissions and integrations. AI-assisted features need representative evaluation cases, including uncertain answers and situations where the system should stop or seek approval.
Agree the release approach, access, documentation and support responsibilities. Define how incidents and future changes are handled. A pilot should have a decision point for refining, expanding or stopping the work.
DATA & ACCESS
Before development, identify the data required for the task, where it is stored and who may access it. Use the least access needed for the agreed workflow, and decide how credentials, logs and third-party services will be managed.
For AI features, discuss whether external model providers will receive business information, how the selected service handles that information and which content must remain outside the workflow. Provider terms and the organisation’s requirements need review for the actual implementation.
Approval controls should reflect the consequences of an action. Preparing a draft and sending a message are different permissions. Changing a record, issuing an instruction or making a financial commitment needs an explicit access and approval model.
QUALITY & OPERATIONS
Use real or approved sample records to describe expected behaviour, user roles and exception paths. Agree what counts as a completed task before development, rather than relying on a vague promise that the workflow will be automated.
Assess answers and actions using representative cases. Include missing information, misleading inputs and requests outside the approved scope. Record known limitations and define when a person must take over.
Agree what is logged, who receives failure notifications and how interrupted work can resume. Data correction, rollback and recovery requirements depend on the application and should be planned with its users.
Clarify code and account ownership, third-party licences, documentation and support coverage. Cloud, API and model usage charges should be visible alongside development and maintenance costs.
SCOPE & INVESTMENT
The complexity of a workflow matters more than the number of screens alone. User permissions, data quality, system interfaces, migration needs, reporting and approval rules all affect the work required. A reliable estimate needs a clear first-release boundary.
Existing software subscriptions and API access may impose additional costs or limits. AI features can introduce usage-based charges and ongoing evaluation needs. Distinguish development cost from hosting, vendor subscriptions, support and future changes.
For an initial discussion, share a short workflow description, the tools involved, the users affected and the result you need. Redacted examples are useful; do not send passwords, private customer records or production credentials through a general enquiry form.
WORK WITH DESHTECH
DeshTech began in 2017, registered as a business in 2019 and incorporated as a private limited company in 2025. We work with Sri Lankan and international businesses and bring website development context to discussions about connected digital services.
For a specialist engagement, discuss relevant work, a demonstration or a scoped pilot that addresses your requirements. The proposed team, responsibilities and delivery terms should be clear before work begins.
COMMON QUESTIONS
Often, no. If a task follows predictable rules and the required systems support the workflow, conventional automation may be simpler to operate. AI should have a defined role that can be evaluated, rather than being added to every step.
That depends on the products, access rights and supported interfaces. Share the system names and the information that needs to move between them. The assessment should confirm feasibility, vendor restrictions and any required subscriptions.
That is a design decision based on the task and its consequences. Access, actions and approval rules must be agreed explicitly. Begin with narrow permissions and a controlled pilot before considering broader autonomy.
A limited first version or pilot can help clarify requirements and expose dependencies. Define what it must demonstrate and how you will decide whether to continue. A prototype is not automatically ready for production use.
Choose measures that match the task, such as completed records, error rates or time spent on a defined process. Record a baseline and comparison period where practical. No productivity or cost-saving percentage is assumed before measurement.
Agree hosting, system ownership, vendor accounts, support coverage and change responsibilities in the engagement terms. An application may need ongoing maintenance and monitoring beyond its initial development.
NEXT STEP
Tell us what happens today, where work becomes slow or difficult and which systems are involved. We can discuss whether an application, a rules-based automation, an integration or an AI-assisted pilot is the appropriate starting point.