Devices serve people — not the other way around
The way we work comes from a set of beliefs about what connected technology is actually for, what good advice looks like, and where the boundaries of our role should sit.
← Back to homeWhat we came here to do
Smart Node Base was built around a fairly simple observation: connected devices are genuinely useful when chosen for the right reasons, and considerably less useful when chosen for the wrong ones. Most of the time, the wrong reasons aren't malicious — they're just the natural result of a process that starts with equipment rather than context.
We exist to shift that starting point. Independent planning — done before any device is purchased, by someone with no financial stake in which device you choose — creates a different kind of foundation for a connected setup. We think that matters, and it shapes everything about how we work.
This page explains the thinking behind that position. Not as a pitch, but as a straightforward account of where we're coming from.
What we think is possible
We believe that most households and small facilities in Japan could benefit from a modest, well-considered connected device setup — one that addresses something real, sits within the existing infrastructure, and doesn't create new complexity faster than it resolves old problems.
We also believe that getting there doesn't require a large investment, a complete renovation, or a vendor relationship. It requires a clear picture of what the space actually needs, and a plan built around that picture rather than around a catalogue.
How we think about our role
Our role is limited by design. We are planners, not installers. We produce written plans and then step back. This isn't a limitation we apologise for — it's the point. An advisor who also installs has a different relationship with the scope of work than one who only advises.
By keeping our role clearly on the planning side, we can give clients something genuinely independent: a document that describes what the situation calls for, without any commercial interest in how it gets implemented.
What we actually believe
Scope should be earned, not assumed
A connected device setup should cover exactly what the situation calls for — not what a product line offers, and not what seems impressive. We've found that the setups people use most consistently are the ones that started with a genuine need, not an aspiration to a certain kind of home or facility.
Reasoning should accompany recommendations
When we recommend a device or configuration, we explain why. Not to justify ourselves, but because clients who understand the reasoning can make better decisions later — when circumstances change, when something stops working, or when they want to extend the setup without starting over.
Privacy is part of the design, not an afterthought
Connected devices generate data. That's often the point. But it means network design, data handling, and device permissions need to be considered before installation — not patched afterwards. We treat this as a structural part of the plan, not a footnote.
Existing things have value
Routers, switches, older devices, existing wiring — we work around what's already there wherever the situation allows. Replacing functional infrastructure is sometimes necessary, but it's never our default. Respecting what exists is both practical and, we think, the right starting position.
Clients should leave with something durable
The document we produce at the end of an engagement should still be useful in two years. That means it can't just describe what to buy — it has to document why, and what the choices depend on, so that the reasoning survives even if specific products change.
Honesty about limitations matters
There are situations where a planning engagement won't add much value — where the need is simple and clear, and a client is well-positioned to handle it themselves. We say so when that's the case. An honest assessment of fit is more useful than a project undertaken for the sake of having a project.
How these beliefs show up in the work
We structure sessions around questions before recommendations. The first session of any engagement is mostly listening.
Every recommendation in the written plan includes a reason and, where relevant, an alternative that was considered and set aside — with an explanation of why.
Every plan covers network segmentation, data handling basics, and device permission settings relevant to the chosen devices — before any purchase is made.
We start with an inventory of what's already installed or owned. Plans are built around that baseline, with replacements recommended only when there's a clear functional reason.
We don't extend the scope of an engagement without a conversation. If the situation turns out to be simpler than expected, the engagement can be concluded early.
The written plan belongs entirely to the client. It can be shared with any installer, used for independent procurement, or set aside. There's no continued dependency on us.
Every setup is built around a specific situation
Connected device planning that doesn't account for who lives or works in the space tends to produce systems that work technically but not practically. A setup suited to a single occupant working from home looks different from one suited to a family household, a shared business premises, or a production facility on a rotating shift schedule.
We spend time understanding the human context before we start talking about devices. What are the actual routines? What causes friction? Who interacts with the space, and in what ways? The answers shape everything that follows.
There's no standard timeline for adoption
Some clients are ready to implement everything in a plan within a month. Others want to move through it gradually, one phase at a time, over a year or more. Some will pause and return to it later. All of these are fine.
Plans are written to be useful at any pace of implementation. The reasoning stays relevant even if the specific products recommended have been updated by the time a client comes back to it. We try to anticipate this and document accordingly.
Change driven by what we observe, not by what's new
The connected device market moves quickly. New protocols, new platforms, new device categories appear regularly. Some of these developments are genuinely useful improvements. Others are incremental or add complexity without proportionate benefit.
We update our planning frameworks when we observe that a change in the landscape meaningfully affects the advice we'd give. We don't update them to incorporate novelty for its own sake. The question we apply is consistent: does this change what a client in a typical situation should actually do?
Protocol developments (Matter, Thread, Zigbee, Z-Wave), platform changes that affect device compatibility, and network hardware developments relevant to residential and light commercial settings.
Products released primarily for marketing cycles, feature additions that add complexity without solving an actual problem, or trends that haven't proven durable in practical settings.
A change makes it into our planning frameworks when it would visibly alter the advice we give to a typical client. Until then, we note it as a development to watch.
What honesty looks like in practice
Transparency in our context means being clear about what we know, what we don't, what the plan is based on, and where uncertainty exists. It also means being clear about what we're not — we're not installers, we're not support technicians, and we're not a long-term service relationship.
We try to make the boundaries of each engagement explicit before it begins. If something falls outside what we do, we'll say so and, where we can, point toward who might help.
What the plan is based on
Plans note the information they were based on and the date they were produced. If conditions change materially — the client moves, the network changes, a key device is discontinued — the plan may need revisiting, and we say so explicitly.
Where uncertainty exists
When a recommendation depends on a factor we can't verify — such as the exact wiring configuration of a site we haven't visited — we note the assumption and flag what would need to be confirmed before proceeding.
Planning works better as a conversation
The most useful plans we've produced came from engagements where the client was actively involved — sharing context, pushing back on early assumptions, and asking questions at each stage. A planning engagement isn't something we do to a client; it's something we do together.
This means we try to keep the process legible throughout. Documents are shared in draft before they're finalised. Sessions end with a summary of what was discussed and what will be addressed next. Nothing is presented as settled until the client has had a chance to respond.
We also work alongside installers, facilities managers, and in-house IT staff rather than in parallel to them. If a client has an existing relationship with an installer they trust, the plan we produce can be handed to that installer directly.
The goal is a setup that the client understands and can manage. That means the people responsible for maintaining it need to have been part of shaping it — or at minimum, have access to clear documentation of why it was designed the way it was.
Planning for the setup you'll still be using in five years
A connected device plan that optimises entirely for the present tends to age poorly. Device ecosystems shift. Protocols change. The space evolves. A plan built with some awareness of this — documenting the reasoning, noting which recommendations depend on current conditions, flagging which choices leave future options open — holds up considerably better.
We're not in a position to predict the future of the connected device market. But we can produce plans that are honest about what they assume, and that make those assumptions explicit enough for a client to revisit them later without needing to start from scratch.
Documented reasoning
Plans that explain why are easier to update than plans that only explain what.
Open-standard preference
Where there's a choice between proprietary and open-standard solutions of comparable capability, we tend to recommend the open-standard option for its longevity.
Conservative phasing
Beginning with the highest-impact, lowest-complexity elements means the setup is functional and maintainable before anything more involved is added.
How our approach translates into what you experience
The beliefs outlined here aren't abstract. They show up in specific, concrete ways in how every engagement is structured and delivered.
You'll be heard before you're advised
Every engagement begins with structured listening. We ask about your current situation, your routines, your constraints, and what you're actually trying to address — before we offer any recommendations.
You'll understand why, not just what
The written plan you receive will explain the reasoning behind each recommendation. You shouldn't need to take anything on trust — the plan should be readable and internally consistent.
The plan is yours, unconditionally
Once the engagement concludes, the document is yours entirely. Use it with any installer, share it with a facilities team, or set it aside. We have no ongoing interest in how you use it.
We'll tell you if it's not the right fit
If your situation is straightforward enough that an independent planning engagement wouldn't add meaningful value, we'll say so at the outset. We'd rather be useful than billable.
If this resonates, we'd be glad to hear from you
The best way to know if an engagement makes sense for your situation is to describe the situation. There's no obligation attached to getting in touch, and no pressure to commit to anything in that initial conversation.