The 2011 introduction, as written
The post opens with a confession familiar to anyone who has ever procrastinated a blog: the author had “been thinking to start blogging for the last two years”, and finally got the chance the day WordPress was installed on the company server. WordPress itself gets a rave — “the rising technology in this era of IT… it lets you build a website in a second” — which, from a company that would spend the next decade hand-engineering bidding platforms, is an endearing place to have begun. That very installation, fifteen years on, is the source this entire archive was rescued from.
The team, counted
The post’s most valuable cargo is a precise census of the company in mid-2011 — a development team in Nepal with a contact presence in the USA, nineteen people in all, listed with obvious affection:
- 10 programmers — “PHP, MySQL, Ajax and jQuery + Linux stuff”;
- 3 graphic designers — “the charming wealth of our company”;
- 3 PSD-to-HTML specialists — “I can’t believe how fast their hands move”;
- 2 QA testers — “software without testing is nothing, so our two software guards take its job”;
- 1 technical project manager — “the key person of our company”.
That structure — programmers, designers, slicers, QA, a TPM — is exactly the team that appears, in threes and fours and fives, across the project stories in this archive: Khazaana’s trio, Mummybids’ four, Snapbid’s five.
The voice of 2011
The post promises that the company “never compromises on quality” and “always says yes” to clients — the eager voice of a young studio hungry for work. We preserve the phrasing as history rather than repeat it as policy: the mature version of that instinct, practised today, is almost its inverse — the discipline to say no to a poor fit, and let the production record do the persuading.
Reading it from 2026
Present-day editorial perspective.
Everything this archive documents — the auction platforms, the payment integrations, the mobile era, the property platforms — was built by the company this post introduces, and by the habits visible in it already: testing treated as non-negotiable, projects run by named roles, and a founder-era instinct to write things down. The blog that post opened ran for a decade; this knowledge centre is its continuation.