BE Teck — the technology arm of BE

We close the gaps everyone else learns to live with.

The same problems keep turning up in ordinary daily life. Everyone quietly builds a workaround, the workaround becomes the habit, and nobody ever fixes the thing itself.

We fix the thing itself. Practically, and at the size that actually matters.

This page arrived with seven gaps in it, and no colour. Keep going — each one closes as you reach it, and the colour comes back with it.

01 — Why we exist

Not a tech company. A repair habit that got organised.

BE Teck was formed because people inside BE kept hitting the same walls and kept being told that was simply how things worked. It wasn't. Three rules decide everything we take on, and the third is the one people find hardest to believe.

Rule 01

It has to be real

No demos, no decks, no pilots that quietly die. If a thing cannot survive a full working day in the field, on a bad connection, it isn't finished and we don't call it built.

Rule 02

Big enough to matter

Small annoyances can wait. We take the gaps that cost people time, money or safety every day, and the ones where being wrong has a real consequence.

Rule 03

It isn't about the money

BE Teck exists to give something back, not to extract. If the right answer is to hand a thing over or give it away, that is what we do. Profit was never the point of forming it.

02 — How a gap becomes a product

We find our problems by living them.

Nothing here starts with a market report. It starts with somebody hitting the same wall for the tenth time and finally refusing to walk around it.

◍process-diagram.svg — not found (404)
alt: "how a gap becomes a product"

03 — The family

BE has five arms. This is the one that builds.

Each arm works a different part of the same idea: leave the thing in front of you better than you found it.

BE RealtyProperty. Where the group started, and still the sharpest source of real problems.be.realty BE PowerRenewable energy. Power from sources that renew themselves, where reliability is the entire job.be-power BE4HOPEBe for hope. Our NGO, for animals, and the arm that answers to nothing but need.be4hope BE InfraInfrastructural works. The ground everything else stands on, built to outlast everyone who built it.be-infra

BE TeckTechnology. Formed to close the gaps the other four kept hitting.

BE reads as a verb. That was never an accident. Every arm is an instruction rather than a label: be real, be powered, be hopeful, be built, be technical. The name is the brief.

04 — What we've built

Kshetron.

Buy, sell, build or lend against land in India and you are asked to trust a stack of paper assembled from portals that were each built alone. Kshetron rebuilt that stack as one readable surface.

TerrexThe flagship interface for the fieldpreview ClassicThe proven, simpler way inpreview KaagazDocuments, drafted and signedpreview TempoPeople, work and money, kept in timepreview BEAiA closed-world assistant that cites its sourcespreview

See it from the outside at kshetron.co.in/about.

05 — The work

Five we found in our own work.

The seven gaps on this page were put here on purpose. These five were not. They are real defects in Tempo — the instrument this group runs its own people, work and money on.

Each is written as the same three parts: what the software believed, what was actually true, and what it cost while nobody said anything. That last part is the difference between a gap and a bug.

9 screens asked the same question, separately

Closed

A fact that had no owner

Believed: An order is paid once a single date stamp is set on the task.
Actually: Paying in stages never writes that stamp. When a payment has a schedule, the stages are the payment record — nothing is missing. So every screen asking for the stamp was blind to every rupee that had ever moved in instalments, which is how the largest orders are paid.
It cost: Finance was reminded every three days about money that had already left the account. At the gate, a load paid to the last rupee never reached the guard's list of deliveries to expect, so a fully paid lorry arrived at the barrier unannounced — the exact event that screen exists to prevent.

Nobody reported it. A reminder that is occasionally wrong teaches you to skim the whole class of reminder, and after that the one that matters costs the same as the ones that don't.

the whole note

1 line in a digest, three a day, ringing nothing

Closed

Filed as chatter

Believed: A signature request is a question, and questions belong with comments.
Actually: It is a request for one named person's hand. Until that hand moves, a document, a payment and usually another person are all stopped. Every component in the chain did its job. Nothing failed. The design had simply never been asked what a signature request is.
It cost: The request was held back for the next bulletin — three a day, ringing nothing, one line among a dozen that did not need doing right now. The document sat unsigned, and the payment sat behind the document.

Nobody reported it. The person who had to sign did not know there was anything to report. The person who sent it saw no error and assumed it had landed. Two consistent pictures of the same day, not overlapping at the point where the work was stuck.

the whole note

6 faults in code that had never once run

Closed

Written, and never wired

Believed: There was no way to undo a goods receipt typed with the wrong quantity.
Actually: The code to undo it had been written. It had no callers at all — no button, no menu item, no route. On the same system two more buttons had never appeared for anybody in the whole life of the feature, and text machine-read out of more than a thousand site photographs had never once been looked at.
It cost: Corrections happened on paper, in a note, and in the head of the one person who remembered which entry was the bad one. Wiring the function up took six fixes first: it could drive a store's balance below zero without saying so, and its permission check let anybody whose name was on a row cancel that row.

Nobody asked for the button, because a workaround already worked and had been taught to the next person who needed it. The gap had not closed. It had been staffed.

the whole note

2 unrelated causes behind one complaint, one day

Closed

The complaint names the wrong thing

Believed: The settings link does not work. Reported twice in a single day.
Actually: Nothing was ever wrong with that link. A greeting panel was mounting at zero opacity across the whole window and still accepting every click — only for people who leave the tab in the background, because the animation frame meant to reveal it never fires there. Later the same day, an unrelated second fault: two click handlers on the same menus, and the one that no longer knew where the menu lived closed it a beat before the click could reach the link underneath.
It cost: The page looked entirely normal and nothing on it responded, anywhere, until it was reloaded. Settings took the blame because the profile icon is the first thing most people try.

It was reported accurately and diagnosed wrongly. Fix the first cause, ask "is it working now?", and the honest answer from the person now standing in front of the second one is no — which reads to everybody as the fix having failed.

the whole note

129 of 138 table headings with no case rule of their own

Closed

Capitals are a contrast, not a volume

Believed: One line of styling would put the interface's labels in capitals.
Actually: That line inherits into everything inside it. It capitalised task titles, descriptions, comments people had typed themselves, names, error messages and empty states. For about a week it looked deliberate.
It cost: We read words by their shape, and capitals flatten every outline into the same rectangle, so a capitalised sentence is read closer to letter by letter. That is worst on a phone, outdoors, in sunlight, which is where a great deal of this application is used. Taking the rule back off was a survey rather than a deletion: 129 of the 138 table headings carried no case rule of their own and would have silently lost their capitals with it.

Nobody complained. The request had been granted, so there was nothing obvious to complain about — and a screen stays tiring for as long as nobody puts it into a sentence somebody can act on.

the whole note

of our own tests were green while the bug was still there.

A test that describes the code rather than the rule will defend a defect as loyally as it defends a feature, and it will do it while reporting green.

PASSThe check guarding the "this is paid, close it?" prompt was anchored on the same stale date stamp. It passed for weeks while the prompt failed to appear on exactly the orders it was built for.
PASSThe check written to stop the invisible panel coming back had the comment explaining the fix sitting between the two things it needed to compare, which pushed one of them out of view. It was only caught because the bug was put back deliberately, to watch the check go red. It didn't.

A test you have never seen fail is a test you are trusting on its own word. It takes about a minute to break the thing on purpose and confirm that something notices.

Read the notes 8

06 — Where this is going

The plan is a ladder, not a promise.

By 2050 the aim is that BE is one of India's defining real-estate groups — not the biggest by land, the most trusted — with technology ventures the rest of the industry runs on. Trust is the compounding asset. Land runs out; a reputation for provable, on-time, tamper-evident delivery does not.

That is twenty-four years away, which is long enough for anybody to say anything. So this does not ask you to believe the year. It shows the four rungs between here and there, and what already exists for each of them today. The claim is the ladder, and the rung we are standing on.

Take me to 2050

Twenty-four years, four rungs, seven decisions still open. It comes back.

The rung we are standing on Rung 1 · 2026–2030

Provably the best-run developer in our markets. Tempo runs this group's own money, materials, approvals and signing; Kshetron de-risks land before it is bought; every document we issue is meant to be verifiable by the person holding it. The measure is blunt — zero undocumented rupees, and disputes resolvable from the records alone.

2026–30Provably the best-run developer
2030–35The tools become the industry's
2035–42Multi-venture on the trust rails
2042–50The definition

07 — Talk to us

Have a gap worth closing?

If something in your daily work is broken in a way everybody has stopped complaining about, that is exactly what we want to hear.

Tell us about itbutton does nothing

hello@be-teck.com

Seven gaps, all put here on purpose.
The ones in your day weren't.

2050 rung 1 of 4 · 7 decisions still open back to 2026

BE — the aim

2050.

BE is one of India's defining real-estate groups — not the biggest by land, but the one whose buildings, records and people are the most trusted — with technology ventures that the rest of the industry runs on.

Trust is the compounding asset. Land runs out; a reputation for provable, on-time, tamper-evident delivery does not. Every venture below exists to manufacture trust at a larger scale.

24years ahead of today

Rung 1 of 4where we actually stand

7decisions still open

The line

Three candidates. None of them chosen.

“Building India you can verify.”

candidate 01

“Trust, constructed.”

candidate 02

“By 2050: the builder the record trusts.”

candidate 03

◆One of these becomes the line. Akash picks it; until then the page shows all three rather than borrowing the confidence of a decision nobody made.

The ventures

Five instruments, live. Four names, not yet anything.

The centre is the group. The inner ring is what runs today — you can open every one of them in a new tab before you finish reading this sentence. The dashed outer ring is the candidate ventures for the 2035–42 rung: not chosen, not registered, not built. They are drawn in the colour this page uses for a thing that does not exist yet, which is the same grey it opened in.

a colour means it is live, and the row opens it grey and dashed means it does not exist ◆ means nobody has decided yet

Live today — open any of them

◆ Candidates — none chosen, none started

BE MaterialsProcurement on Tempo's three-way-match rails
BE FinanceConstruction finance underwritten by live project data — lending against records you can verify, not photographs of progress
BE ManageThe building's life after handover, on the same records that built it
BE Power+BE Power, the renewable arm, taken to township scale and metered on NetPulse-class telemetry. The arm exists; this extension of it does not

◆New ventures only where the existing stack gives an unfair advantage. Which of these four — if any — is the 2035–42 decision, and it has not been taken.

The ladder

Four rungs, read downwards, ending on the one we are standing on.

Each rung funds and de-risks the next, and each one carries a today panel: what already exists for it, right now, as things you can open. A rung with nothing under it says so in words rather than being left off the list.

Rung 4

2042
–2050

The definition.

The BE stack is how Indian real estate is expected to operate: verifiable delivery, provable money, land bought on evidence. Whether by market share or by standard, the industry moves to where BE has been for a decade.
BE townships as the reference — places built, financed, powered and managed by the group's own ventures, with the records public wherever the law allows it.

Today

Nothing stands here yet, and nothing should. A rung sixteen years out with something already under it would be a rung somebody had padded. What exists for this one is the three rungs below it, in order.

◆The flag is not chosen: a revenue target, a count of cities, or the trust metric — disputes per crore, bank acceptance, resale premium. The recommendation on the table is the trust metric, because it is the one a competitor cannot buy.

Rung 3

2035
–2042

Multi-venture: everything a township needs.

New ventures only where the existing stack gives an unfair advantage. Four names are on the table — Materials, Finance, Manage, and BE Power at township scale — and none is chosen.
Each would inherit the trust machinery whole: sealed documents, provable money, local AI. That inheritance is the only reason to start any of them.

Today

~~RAIL~~The rails these would run on already carry a real developer's work — goods received, site stores, money that moves in stages, documents that stay provable. a goods receipt you could not undo
~~RAIL~~Money that moved in instalments, and the nine screens that could not see it — the three-way-match and staged-payment rails, written up from the day they broke. the note
~~NONE~~No venture has been started. Nothing is registered, staffed or funded. nothing to link

Rung 2

2030
–2035

The tools become the industry's.

Tempo as the operating system for mid-size Indian builders — the firms too big for WhatsApp and too small for SAP.
Kshetron as the diligence standard: banks and NBFCs accept a Kshetron land report the way they accept a valuation.
Kaagaz verification embedded in RERA and registry workflows, wherever regulation allows it.
BE Realty grows deliberately — fewer, larger, flagship projects that demonstrate the stack. A project you can audit from your phone.

Today

~~LIVE~~Five instruments exist, and each has a public preview a stranger can open right now without an account. kshetron.co.in
~~LIVE~~What the five actually are, in plain words rather than a product page. the note
~~NONE~~No builder outside BE is running on Tempo yet. That is rung 1's job and it is not finished. none yet

◆500 builders is the number on the table for this rung. It has not been agreed, so the page does not print it as a target.

Rung 1

2026
–2030

we are here

Provably the best-run developer in our markets.

Tempo runs all of BE's operations — money, materials, approvals, signing. Substantially true already; the remaining paper is the work.
Kshetron de-risks every land acquisition before the purchase, and the record of the calls it got right becomes the sales deck.
Every BE project delivered with a verification page: any buyer, bank or authority can check any document we issue.
The first ten builders outside BE running on Tempo.
The measure is blunt: zero undocumented rupees, disputes resolvable from the records alone, and a score from the vendors — the people builders usually burn.

Today

~~LIVE~~Kshetron is live and public, with the five instruments behind it. kshetron.co.in
~~LIVE~~Five defects found in our own operations, each written up with what it cost while nobody said anything. They are on the page you came from. the five
~~LIVE~~The habit itself, written down as it happens — how we find our own problems, and what a gap is once you stop walking around it. the notes
~~GATED~~The verification page exists today, behind a sign-in. Nobody outside can check a document with it yet, so there is nothing here to click. not public
~~NONE~~Zero builders outside BE. The first ten have not been approached. 0 of 10

◆Whether the verification page becomes a public promise — every project, every document, checkable by anyone — is not decided. ◆Free pilot or paid from day one, for the first ten builders outside BE. Not decided.

How this page stays honest

A stalled rung will say it stalled.

Every rung above carries an owner, a date and a measure, and gets one honest paragraph a quarter — moved, stalled, or learned. This page reads from that record, so it cannot drift away from the truth on its own. A rung that has not moved will say it has not moved, because a plan that only ever reports progress is a plan nobody is running.

◆Owners and review dates are not assigned to the four rungs yet. Until they are, the quarterly paragraph has nobody's name on it.