logic.gates — the visual language of the platform
how a handful of maths symbols became the design and decision language for the .logic platform, the logic.* product family, and how we explain what iTTD actually does.
∧ architecture · → platform · ⊕ partnerships · ∨ scale · ¬ help
at first we just wanted a name and a logo that felt right — serious enough for enterprise buyers, but with a bit of personality. ITTD LTD literally stands for “Its Tekkers The Dog”. Tekkers is the dog who always showed up, no matter the day. loyal, energetic, caring, hard working. always there. in the good times and if things ever went sideways. the paw is a reminder to build ittd into a company with the same perspective and to look out for everyone - staff, clients and partners - as we go.
and
foundations gate. multiple things must be true at the same time: stable core, clean data, predictable onboarding, and workflows that work in a van, not just in Figma.
multi-tenant engine ∧ iTTD OS ∧ assist ∧ sector packs → when all four hold, a new logic.* vertical is genuinely viable.
- core platform requirements (jobs ∧ routing ∧ docs ∧ auth)
- “we only ship when” criteria for new verticals
- deployment readiness checks inside iTTD OS
- non-negotiables in investor and partner conversations
or
scale gate. once the core is stable, we choose where to grow: logic.fleet ∨ logic.hvac ∨ logic.gas ∨ logic.rental ∨ logic.marine. the platform doesn’t care which comes next — the economics and partnerships do.
logic.fleet live ∨ hvac interest spike ∨ strong WL partner in gas → we can pick the best next move without re-architecting anything.
- logic.* roadmap discussions (which sector next?)
- prioritising WL opportunities by effort vs upside
- “this OR that” choices in product tiers and packs
- showing investors optionality without chaos
not
honesty gate. represents the stuff owners hate but tolerate: manual spreadsheets, stitched tools, opaque pricing, 18-month “roadmaps” that never land. .logic is designed to flip those.
¬ manual onboarding · ¬ mystery pricing · ¬ “we’ll get back to you in Q4” → fewer excuses, more things that actually work.
- “no more…” problem statements on the website
- storytelling around legacy system pain
- .help content focused on removing friction, not adding jargon
- internally: does this feature reduce pain, or add it?
xor
partner gate. some relationships are either/or: either we sell direct into a space, OR we power a WL/OEM partner. we don’t compete with the people we’re powering.
direct logic.hvac rollout XOR “powered by .logic” under someone else’s brand → we choose one route per sector / territory and commit.
- white-label and OEM decision frameworks
- partner conversations (“we’ll be your engine, not your competitor”)
- equity and strategic partner planning
- keeping the brand architecture clean and non-conflicting
implies
flow gate. connects “if this is true” to “then that should happen”. everywhere in .logic: from smart onboarding to assist nudges to how a trial turns into a paying tenant.
trial sign-up → smart onboarding → deploy tenant → real usage data → better assist → a feedback loop the platform can learn from.
- explaining smart onboarding flows
- assist behaviour: conditions → suggestions → actions
- roadmap storytelling (this feature → that outcome)
- value chains in investor and partner decks
simple shapes keep complex things readable: insight vs detail, creative vs technical, reassurance vs hard numbers. they show up across product screens, docs, and decks so your brain doesn’t have to relearn the rules.
- ▲ benefits & owner-level insights
- ◆ .studios creative / narrative elements
- ● support, reassurance, and “how to” steps
- ■ technical details, specs, integrations
pick a gate to see how it shows up inside the .logic platform, the logic.* roadmap, and real-world decisions.
∧ platform architecture
multi-tenant core ∧ iTTD OS ∧ assist ∧ sector packs. if any one fails, it’s not “platform ready” yet.
∨ choosing the next logic.* vertical
logic.fleet today ∨ logic.hvac, logic.gas, logic.rental tomorrow. pick the best mix of demand, WL opportunity, and bandwidth.
¬ removing friction
¬ “please email support to change your plan”. ¬ “we’ll get back to you after the next big release”. ¬ onboarding that needs two on-site days.
⊕ white-label decisions
either we launch direct, or we power a major partner. never both in the same space.
→ smart onboarding → revenue
trial sign-up → smart onboarding → deployed tenant → live usage → better assist → lower churn.
decks, docs, and UI
the same gates show up on investor slides, in web copy, and across the product UI. once you see them, you can’t unsee how the system thinks.