Start a project
[1]

An engineering team that owns what it builds.

WEBTECH.IT is a software team in Jaipur. We design, build and support web platforms, mobile applications, cloud infrastructure and the data systems underneath them and we stay with the work after it ships.

How we are put together

The company is built around its engineers. Around them sit designers, testers, and the people who make sure invoices go out and laptops get replaced before they die.

Nobody hands a project on at the end of a phase. The people who design a system are the people who build it, and the people who get called when it misbehaves.

We take on work we can staff properly and turn down work we cannot. That is the whole of our capacity planning, and it is why the answer is sometimes no.

Most of our work arrives through somebody we have already built something for. We have never had a sales team, and it has never seemed to hurt.

[2]

Six rules we hold each other to.

These are pinned to the wall by the kitchen, which is either sincere or a cliché depending on how the week is going. They do get quoted in code review.

  • 01

    Say the inconvenient thing early

    If a date will not hold or a feature is a bad idea, you hear it that week not in a retrospective after it has already cost you money.

  • 02

    Estimate honestly

    We would rather lose a pitch than win it on a number none of us believe. A cheap estimate is just an expensive argument scheduled for later.

  • 03

    Leave it better documented than we found it

    Including the parts we did not write. Anyone who joins the project after us should be able to run it locally on their first afternoon.

  • 04

    No heroes

    If one person is the only one who understands a system, that is a fault in how we are working, not a sign of how good they are.

  • 05

    Whole problem, not a ticket

    People who understand what a system is for will beat people who each understand one item on a board. Everyone on a project knows the business behind it.

  • 06

    Finish things

    A feature that is ninety per cent done is nought per cent shipped. We close work before we open more of it.

What we are trying to do

Write software that is still affordable to change in three years.

Most systems become expensive to modify long before they become old, and that is almost always the result of a decision somebody made in the first month. We spend a disproportionate amount of our time on those early decisions, because they are the only ones that are cheap to get right.

Where we are heading

Be the team that gets called back.

We would rather be the studio a company comes back to than one it tried once. Growth here means longer relationships and deeper knowledge of the businesses we already work with, rather than a longer list of names nobody remembers.

Want to see whether we would suit each other?

The quickest way to find out is to tell us what you are trying to build. No deck, no discovery invoice just a conversation about the work and whether this team is the right one to do it.

Get in touch