Four departments, each answerable for its part
Lattice Nepal is organised by department, not by title. The software we build, the servers we run, the clients we answer to, and the journal we publish — each sits with one desk that owns it. We name the desks here, not the people at them: staff change; the desk that answers does not.
What happens after you write
- 01
Scope
We agree the exact thing to build and what "done" means before any code is written.
- 02
Build
We ship in small, reviewable pieces you can see early, not one big reveal at the end.
- 03
Ship
We deploy to a real server, with a runbook anyone on the team can follow.
- 04
Run
We host it, back it up, and fix it when it breaks. The work does not stop at launch.
What we build and run
Engineering
The websites, web apps and mobile apps that leave this studio are Engineering’s to answer for. The department writes the frontend, the API and the database as one system, ships in small reviewable pieces, and signs off nothing it would not run itself. When a client site has a bug, this is the desk it lands on.
- Code review on every change before it ships
- One back end shared by site and app, so the data never disagrees with itself
- Handover with documentation a new developer could pick up
Hosting & Operations
Servers, backups, certificates and uptime — on shared hosting, VPS, or cloud on AWS, Google Cloud, Azure or DigitalOcean, wherever the project lives. This desk watches the machines so clients never have to — when a certificate is near expiry or a disk is filling, Operations already knows. What Engineering ships, Operations keeps online.
Client Services
Scope, written estimates, and plain answers about cost and timeline. Client Services is accountable for what we put in writing and when it lands — if a date slips, this desk says so before you have to ask.
What we publish
The journal carries the company’s name on every article, so it answers to a different standard than client work: the reader’s.
Editorial
Sourcing, editing and fact-checking every article in the Lattice journal to a two-source standard. Editorial is accountable for the accuracy of what we print — and for the corrections, which run under the same byline standard as the original piece.
Whatever it is, a department owns it.
A bug on a client site goes to Engineering. A server worth worrying about goes to Operations. A question of scope or cost goes to Client Services, and a correction goes to Editorial. Write to us once — the right desk picks it up.