About Insteller

An engineering firm built to work inside other people's businesses.

Insteller (Pvt) Ltd is a software engineering company registered in Galle, Sri Lanka. We build and run systems for agencies and consultancies that need capacity they can stand behind, and for the companies that need those systems built directly.

  • Galle, Sri Lanka

    Single delivery base. One office, one team, one contracting entity.

  • GMT +5:30

    Full working-day overlap with Australia, Asia and the Middle East, mornings with Europe.

  • Galle, Sri Lanka

    Insteller (Pvt) Ltd, incorporated in Sri Lanka, with one delivery team in one place.

  • Five practices

    Salesforce, AI engineering, full-stack, mobile and quality engineering, under one supplier relationship.

The firm

One supplier across the disciplines that usually need three.

Most technology work of any size crosses more than one practice. A product needs a front end, a platform and an integration. An AI feature needs somewhere to live. A Salesforce estate needs the systems around it to behave.

Insteller was set up so that work crossing those lines does not need a second supplier and a third contract. Salesforce, AI engineering, full-stack engineering, mobile and quality engineering sit in the same company, under the same delivery standard and the same commercial relationship. Where two of them meet, the seam is ours to solve.

That structure suits both of the buyers we serve. An agency wins work that spans a product build and a platform integration and needs one partner that can take all of it. A direct client wants a system taken from architecture to production and then kept running, without managing a panel of specialists to do it.

We are deliberately not a body shop. Engineers are allocated to an engagement rather than shared across several, contracts and confidentiality are settled before anyone starts, and the people who begin a piece of work are the people who finish it.

What we are known for

  • Production Salesforce estates, including CPQ, kept running and extended
  • Full-stack platforms taken from architecture to live service
  • Applied AI built as a product feature rather than a demonstration
  • Systems in regulated and audit-sensitive environments
See selected work

Base and group

Based in Galle, structured to be easy to contract with.

Where we sit determines the working day you get, and how we are structured determines who you are accountable to. Both are worth being clear about before a first call.

Galle, Sri Lanka

Delivery runs from a single base in Galle rather than a distributed network of contractors. One office, one team, one standard of supervision.

  • Registered office at 127/1 Dolagawaththa, Mampitiya, Galle
  • Engineers employed by the company, not sourced per project

Your working day

Galle sits at GMT +5:30. That gives a complete overlap with Australian and Asian business hours and a working morning with Europe and the United Kingdom.

  • Overlap hours agreed in writing at the start
  • Standup held in your timezone, not ours
  • An escalation path outside agreed hours

The wider group

Insteller is part of a small group of engineering companies under common ownership. Hiring standards, engineering practice and delivery discipline are shared across it.

  • Your contract, staff and accountability sit with Insteller
  • Access to a wider engineering bench where a niche skill is needed
  • Any involvement beyond Insteller is disclosed, never assumed

How delivery is run

The operating model is the same whichever way you engage us.

Dedicated people, a managed pod or a scoped project, delivered under our name or yours. The model changes who directs the work. It does not change how the work is run.

  1. 01

    Named people, not a bench

    Every engagement is staffed with specific engineers at agreed seniorities. You know who is on the work and you deal with them directly.

    Staffing

  2. 02

    One accountable lead

    A single point of accountability for the engagement, responsible for the plan, the quality bar and anything that needs escalating.

    Accountability

  3. 03

    Your process, not ours

    Engineers work in your repositories, your tracker and your review gates. Where you have no process to adopt, we bring one and document it.

    Operating model

  4. 04

    Written cadence

    Agreed overlap hours, standup in your timezone, progress in a form you can forward to your own client without rewriting it.

    Reporting

Engineering principles

Six positions we hold on every engagement.

These are the things we argue about internally and the things a client can hold us to. They apply to a two-week change as much as to a twelve-month build.

01

Diagnose before changing

On a live estate the reported fault and the actual fault are rarely the same thing. We find which layer it belongs to before anyone edits code, configuration or data.

  • Root cause
  • Evidence

02

Build for the next engineer

Code is written to be read by whoever inherits it, including your own team. No private conventions, no cleverness that needs the author present to explain it.

  • Readability
  • Handover

03

Own the failure path

Integrations break, networks drop and uploads fail. We design what happens then, because that is the part an operations team lives with.

  • Resilience
  • Recovery

04

Keep the estate coherent

A change to a pricing rule reaches the ERP. A sharing change reaches the portal. We treat a system as one connected thing rather than a set of modules.

  • Architecture
  • Impact

05

Prove it outside production

Work is demonstrated in a sandbox or a staging environment against realistic data before it is released, on the client release cadence rather than ours.

  • Sandboxes
  • Regression

06

Say what is actually true

Estimates, risks and slippage are reported as they are. A client hearing bad news early can act on it. A client hearing it late cannot.

  • Reporting
  • Escalation

Where we draw the line

What we will not do.

Commitments are easier to judge when the limits are published alongside them.

We do not present a team we cannot staff

If the seniority or the skill is not available for your start date, we say so. Proposals name people and availability rather than describing a capability in the abstract.

We do not subcontract quietly

Work is delivered by our own people. Where a client engagement genuinely requires a third party, it is disclosed and agreed in writing before it happens.

We do not take your client relationship

On white-label work we have no client-facing presence unless you ask for one. Your name stays on the delivery and the relationship stays yours.

We do not claim certifications we do not hold

Our security and confidentiality posture is written down and open to questioning. Where a control is a practice rather than an audited certification, we describe it as one.

Our security and confidentiality position is set out in full on thesecurity page, including how we handle client data, access, devices and incidents.

Next step

Talk to the people who will do the work.

Send the requirement and the timeframe to info@insteller.com, or use the enquiry form. You will get a named team, availability and a start date.