A software company organized around what it builds.
ITLC builds business software: packaged products for specific operations, a platform they run inside, and an engineering practice for what packaged software cannot cover.
- Products for property, commercial rental and accommodation operations
- A platform providing the account, organization and access model beneath them
- A services practice for software that has to be built rather than bought
What ITLC is.
ITLC is a business software company. It sells software it has built, and it builds software for organizations whose requirements no packaged product covers. Those are two different businesses, and ITLC runs both deliberately rather than treating one as overflow from the other.
It is a product company
ITLC Housing, ITLC Plaza and CityHostels are packaged software with their own roadmaps, sold to organizations whose operations they were designed for.
It is also an engineering practice
Where an operation is genuinely particular, ITLC designs and builds software for it — as an engagement, scoped on its own terms, not as a customisation of a product.
The two are kept apart
A packaged product is not forked for one customer, and an engagement does not quietly become an unsupported version of a product. Keeping that line clear is what lets both stay maintainable.
How the four layers relate.
Everything ITLC publishes sits in one of four layers. They are easy to run together, and they are not the same kind of thing.
- Products
- Packaged software you activate and use. Housing, Plaza and CityHostels.
- Solutions
- Which of those products suits the kind of operation you run. A framing, not something to purchase.
- Platform
- The account, organization and access model the products run inside. Not sold separately.
- Services
- Work ITLC's team performs for you, when what you need has to be built.
Products are activated per organization and nothing is bundled. Services are scoped per engagement and are never included in a product subscription.
How ITLC thinks about software.
These are not values on a wall. They are the decisions that shaped the products, and they are visible in how ITLC describes them.
- 01
Build for the operation, not the category
A housing development sells a unit once; a plaza rents the same unit repeatedly. Those are different businesses, so ITLC built different products rather than one that half-fits both.
- 02
Keep boundaries explicit
What a product covers, what it does not, and where an engagement begins instead are stated rather than left to a sales conversation.
- 03
Reuse the foundation, not the solution
Products share an account and organization model so they behave consistently. They do not share each other's records, and ITLC does not claim they do.
- 04
Say what is true, including when it is less
ITLC publishes no customer counts, no uptime figures and no certifications, because none have been verified. Where a category name promises more than ITLC offers, the page says so.
- 05
Write software that can be changed
A requirement that never changes is rare. What gets built assumes it will be revisited, and is handed over in a state where someone else can.
Who ITLC builds for.
The products serve organizations that run physical operations and are held back by how their information is organized rather than by how hard they work.
Property developers and housing societies
Organizations laying out projects, selling units and carrying customers through to ownership.
Commercial property operators
Teams running plazas and commercial buildings where occupancy and recurring rental work drive the operation.
Accommodation businesses
Hostel owners and operators presenting and running accommodation, and the people looking for somewhere to stay.
Organizations with requirements nobody sells
Businesses whose process is specific enough that the right answer is software built for it.
Talk to the people who build it.
Whether you are looking at a product or need something built, the useful starting point is the same: how your operation actually runs today.