About
The company that runs this service, and the principal who leads engagements.
The company
- Company
- Reflerd Inc.
- Registered address
- Osaka, Japan
- Founded
- June 3, 2019
- Business
- Operates re:flerd, an embedded advisory practice for IT projects, with a focus on alignment, agreement, and delivery support.
- Representative
- @nabbisen
Company overview
Reflerd Inc. operates re:flerd, an embedded advisory practice that works in the gaps between business strategy, operations, and technology delivery. The stance is to keep work moving without rushing it, and to leave behind structures in which everyone involved can act on solid ground.
Principal profile
About the practitioner who actually does the work, and the stance behind the practice.
Where the name comes from
re:flerd combines three roots. "re" stands for reliability engineering — a posture of designing for systems that cannot afford to stop. "fler" is the Norwegian word for "more than one", which mirrors the practice of holding multiple stakeholder positions in proportion. "d" is daemon: a quiet companion process that does its work in the background.
Stance
Close enough to the work to understand it, far enough back to keep perspective. Decisions stay inside the organisation; the work is to organise the material so the call can be made well. Failure is not framed as someone's fault — the energy goes into structures in which failure is harder.
Where we add the most value
The strongest entry points are the start of new projects (before the structure sets) and the first signs of trouble (before fires spread). Domains: finance, insurance, healthcare, manufacturing, public sector, infrastructure, logistics, and the core of SaaS businesses — work that cannot stop, with multiple teams that need to converge.
What we won't take on
We don't sell hours as a substitute for judgement, absorb responsibility on someone's behalf, look for someone to blame, or sell through performance. Drawing the line first turns out to be where trust starts.
Why I can support these discussions
I do not approach projects from a single angle. Strategy helps clarify purpose, priorities, decision criteria, and trade-offs. Architecture connects business, product, operations, development, and organisation as a single structure — not isolated parts. Audit and risk thinking surfaces failure modes, accountability gaps, and governance concerns before they become expensive. Practical dialogue with non-IT stakeholders and actual users connects real-world business pain to buildable requirements. These perspectives together — rather than any one of them alone — are what make it useful to consult across business, product, technology, and organisation decisions at the same time.
Talk to us
We can start from organising the situation. No prep deck, no internal sign-off needed beforehand. Whatever you can share is enough to begin.