Westlands · West Park Towers · 8th floor
ISO 9001 procurement standards ● Authorised Cisco · Fortinet · Palo Alto · Dell EMC partner ● Twelve specialised practices · one operating discipline ● Direct vendor partnerships across infrastructure & security ● Engineering Kenya's public-sector infrastructure since 2018 ● ISO 9001 procurement standards ● Authorised Cisco · Fortinet · Palo Alto · Dell EMC partner ● Twelve specialised practices · one operating discipline ● Direct vendor partnerships across infrastructure & security ● Engineering Kenya's public-sector infrastructure since 2018 ●
Nairobi · Est. 2018
A document of operating promises

A Quiet Kind of Excellence.

Four operating promises. They look short on the page. Honouring them is the work across every cabinet, every cable, every cutover, for the institutions that have to keep running.

Read The Four Promises
Designed before deployed Installed by certified engineers Maintained past handover Direct vendor partnerships Designed before deployed Installed by certified engineers Maintained past handover Direct vendor partnerships

Most infrastructure failures aren't engineering failures. They're integrity failures promises made at sale that quietly evaporate during delivery.

The four promises that follow are not aspirational. They are operating constraints, accepted as the cost of taking the work.

Four operating promises

The discipline that holds across mandates.

One firm, one team, one set of standards applied to every cabinet, every cable, every cutover, regardless of contract size.

01

Designed before deployed.

Network infrastructure that's improvised on site is the infrastructure that fails first.

Every mandate begins with real architecture — drawn, costed, stress-tested before a single cabinet is opened. Low-level designs route every cable run. Bills of quantity itemise down to the patch panel. Vendor matrices justify each piece of kit on price, performance, and parts availability.

None of this is window-dressing. The design is the contract — the documentation that lets the same team install on Monday what they specified on Friday.

02

Installed by our own engineers.

Subcontracting dilutes accountability at every handoff. We don't subcontract the work that matters.

The engineers who draw the design are the engineers who pull the cable, set the cabinets, terminate the patches, configure the switches, run the cutover. Each is certified on the kit they're working with — Cisco, Fortinet, Palo Alto Networks, and the rest of the alliance list.

A senior is on site every day a mandate is active, signing off as the work lands. No relay between sale and delivery.

03

Maintained past the handover.

The fiction in this trade is that infrastructure gets delivered. It doesn't. It gets cared for.

Most mandates carry multi-year support agreements. Documented SLAs with named escalation tree. Monthly preventive maintenance. Quarterly capacity reviews. A single named lead engineer accountable for the account.

Same engineers who built the network. Same parts pool we set aside at install. Networks we put in our first year are still under our care.

04

Vendor relationships that compound.

A vendor logo on a slide is decoration. A vendor relationship that gets a part on a plane overnight is infrastructure.

We hold authorised-partner status with the vendors whose kit we deploy. Each authorisation is a working contract — covering protected pricing, a parts pool, and a named escalation path into the vendor's own engineers.

The first two save the institution money. The third saves the institution.

Side note

We don't compete on the lowest bid. We compete on whose runbook the duty engineer is reading at three in the morning.

— TechSource Point, internal compass
Authorised partners

The names behind the work.

Selected partnerships · current
Cisco·Fortinet·Palo Alto·Dell EMC·VMware·Microsoft·Huawei·Check Point·Avaya·HP·Siemon·Ubiquiti·Giganet

Each authorisation is a working contract. Pricing protected. Parts pool accessible. Escalation paths named.

Have a project
that has to land?
Brief us.

Tell us about the mandate; the scope, the timeline, the constraints. A senior engineer will respond with a real conversation, not a sales pitch.

Or email info@techsource.co.ke
Brief our engineers
Step 1 of 4

What's the mandate?

Pick the closest description. You can clarify in the next step.

How big?

A rough idea is fine — we'll scope properly during the brief.

When do you need it?

If you're exploratory, that's fine — we'll send you our credentials pack instead.

How can a senior engineer reach you?

A senior engineer will respond within one business day.