SOFTWARE. DATA. BUSINESS TECHNOLOGY.Sri Lanka · Let’s connect
GoklyLet’s talk

Service packages

A clear starting scope.
A considered next step.

Choose a focused starting point for your website, software, business systems or data project. Review what the work can include before preparing your brief.

Compare the packagesHow quotations work
ROOTED IN SRI LANKA. BUILT AROUND YOU.08 / Service packages

PURPOSE BEFORE FEATURES

Choose the right starting point.

These are proposed starting scopes to discuss. Availability, exact deliverables, price and timing are confirmed in writing before any work begins.

YOUR DIGITAL FRONT DOOR01

Business website foundation

A service-led business that needs a clear, credible company website.

An agreed core website, ready for your team to own.

Proposed deliverables

  • Page plan for up to five core pages, with content responsibilities agreed first.
  • Responsive design and implementation with service and enquiry journeys.
  • Agreed page titles, descriptions, redirects and indexing checks.
  • Browser review, launch checklist and a practical handover.
Scope boundaries & quotation inputs

Outside the starting scope

  • Copywriting, photography, translations and content entry beyond the agreed allowance.
  • Hosting, domains, licences and ongoing maintenance unless itemised.
  • Ecommerce, payments, customer portals and custom integrations.

What shapes the quotation?

Page count, supplied content, editing needs, forms and any existing site.

How the work is reviewed

Review the agreed pages, navigation, mobile layout and enquiry path before launch.

Written quotation after a requirements review.

Discuss this packageExplore the related service
CONNECT YOUR OPERATIONS02

Business systems discovery

A business exploring how to connect stock, sales, purchasing and invoicing.

A reviewable workflow and requirements brief before committing to a build.

Proposed deliverables

  • Map one agreed core workflow and the people who use it.
  • Document key records, approvals, access roles and reporting needs.
  • Identify data migration, integration and rollout considerations.
  • Prepare prioritised requirements and a proposed implementation scope.
Scope boundaries & quotation inputs

Outside the starting scope

  • Production ERP implementation, migration or third-party system configuration.
  • Accounting or tax advice, licences and integrations not in the written scope.
  • A guaranteed implementation price before requirements are reviewed.

What shapes the quotation?

Current tools, users, branches, transaction volumes and the workflow to explore.

How the work is reviewed

Your nominated owner reviews the workflow, priorities and open decisions.

Written quotation after a requirements review.

Discuss this packageExplore the related service
MAKE YOUR INFORMATION USEFUL03

Data readiness & reporting plan

A team with scattered exports or inconsistent reports that needs a reliable starting point.

A defined route from agreed data sources to a reporting dataset.

Proposed deliverables

  • Inventory the agreed sources, access needs and reporting questions.
  • Review a representative sample for formats, missing fields and duplicates.
  • Define quality rules, reporting measures and refresh expectations.
  • Prepare a pipeline outline, ownership notes and a scoped next phase.
Scope boundaries & quotation inputs

Outside the starting scope

  • Continuous production pipelines, cloud consumption and platform licences.
  • Full data cleansing or migration beyond the agreed representative sample.
  • Guessing missing values or guaranteeing accuracy of unverified source data.

What shapes the quotation?

Source types, sample availability, volumes, refresh needs and report owners.

How the work is reviewed

Review the source map, quality findings, metric definitions and proposed next steps.

Written quotation after a requirements review.

Discuss this packageExplore the related service
DEFINE THE RIGHT BUILD04

Custom application discovery

A team that needs an internal tool, web application or mobile application scoped clearly.

A prioritised specification and delivery outline for a useful first release.

Proposed deliverables

  • Define the users, central problem and first-release priorities.
  • Map the main user journeys and agreed screen concepts.
  • Identify integrations, permissions, data and operational requirements.
  • Prepare acceptance criteria, dependencies and a proposed delivery sequence.
Scope boundaries & quotation inputs

Outside the starting scope

  • Production application development, app-store publication and ongoing support.
  • Third-party API subscriptions, hosting and licences.
  • Features or detailed screen designs beyond the agreed discovery scope.

What shapes the quotation?

Target platforms, main users, existing systems, feature priorities and constraints.

How the work is reviewed

Your project owner reviews priorities, user journeys and acceptance checks.

Written quotation after a requirements review.

Discuss this packageExplore the related service

NO ASSUMPTIONS IN THE SMALL PRINT

Know what you’re
agreeing to.

A discovery package produces an agreed plan; production implementation is a separate phase unless the quotation explicitly includes it. The website package includes implementation of its agreed core pages.

Each quotation should identify outputs, review points, dependencies, responsibilities, exclusions and any third-party charges. Your optional budget range helps shape a discussion and does not commit you to a purchase.

Read the project planning guides

For ongoing device and office IT support, explore the separate support plans and guide prices.

LET’S MAKE IT HAPPEN

Have a different requirement?
Let’s define it together.

Tell us what you want to improve. We’ll explore the possibilities and agree a practical way forward.

Start a conversation
WhatsApp