Why do stock databases confuse organizations?
TimeWaver ships with over a million database entries — and almost none of them were written for you. They were authored by medical, homeopathic and psychological practitioners, in the working languages of their own disciplines, for readers who share that grounding. A homeopath reads a remedy entry and sees a rich, precise picture. A leadership team reads the same entry and sees a foreign phrase.
The consequence is predictable. An organization runs a scan, receives entries in vocabulary nobody in the room can locate, and the outputs feel arbitrary. Run that experience three times and skepticism hardens — not because the instrument failed, but because the rubric belonged to someone else. This is the single most common reason corporate TimeWaver adoption stalls, and it has a structural fix.
What is an organization-owned database?
An organization-owned database is a custom TimeWaver database whose entries are written in your vocabulary — drawn from your vision documents, your strategy frameworks, the phrases your founders actually use. Instead of a million borrowed entries, it holds a curated set authored around 5–7 measurement metrics the whole team defines and owns: the dimensions of culture, leadership and direction that matter in your house, named in your words.
From then on, the machine answers in language your people already use. A scan stops being an act of translation and becomes an act of recognition. As we put it in every engagement: "When the rubric is yours, the outputs make sense."
How is a custom database built?
The build is a structured collaboration over roughly six months, in seven stages:
- Discovery. We immerse in your vision language, frameworks and strategy documents — the raw vocabulary of the future database.
- Metric definition workshops. Leadership and core team define the 5–7 metrics, debating the words until they are genuinely owned.
- Collaborative entry authoring. Entries are drafted in structured language — your team supplies vocabulary and judgment, we supply entry craft.
- Version 1 build. We handle the full technical construction of the database on your system.
- Pilot. Version 1 is used with real people and real contexts, and every confusing output is logged as design input.
- Iteration. Entries are rewritten, split, retired and added based on pilot evidence.
- Version 2 + handover. The refined database ships with SOP documentation — authoring rules, maintenance rhythm, versioning — and is handed to your team for good.
How are the metrics co-designed?
The metric workshops are the heart of the build, because a metric only works if the whole team means the same thing by it. Each candidate metric cycles through the same loop: leadership proposes a dimension, the room debates the wording, entries are drafted against it, a test scan shows how the entries read in practice, and the wording is refined. The loop repeats until the metric survives contact with a real reading — then it enters the database.
Wondering whether your language is database-ready? Bring your vision documents to a scoping conversation — we will tell you honestly what a Phase 2 build would look like.
Enquire About a BuildWho should build one?
A custom database is a Phase 2 and 3 undertaking — it presumes the foundations are in place. The organizations that get full value share three traits: they are past the foundations stage with a core team trained to run and decode analyses confidently; they have real vision language — frameworks and vocabulary with genuine internal currency; and they intend to use the instrument on a rhythm, not as a one-off experiment. If that is not yet you, the Foundations training on the programs overview is the right first step, and the database can follow.
What does it cost?
Two phases, each scoped and confirmed separately, each roughly three months:
- Phase 2 — Discovery, design and version 1: SGD 32,000–45,000, scoped precisely at kickoff. Covers discovery, the metric workshops, collaborative authoring and the full version 1 technical build.
- Phase 3 — Pilot, iteration and handover: SGD 35,000–50,000. Covers the live pilot, the iteration cycle, version 2, SOP documentation and complete handover to your team.
Each phase stands on its own decision — you confirm Phase 3 only after Phase 2 has delivered. A 10% administrative fee applies before taxes, and payment is made before delivery.
Stock databases vs your own database
| Dimension | Stock databases | Your own database |
|---|---|---|
| Language | Medical, homeopathic and psychological vocabularies from other disciplines | Your vision language, frameworks and everyday phrases |
| Ownership | Authored by and for other practitioners — the rubric is theirs | Authored with your team around 5–7 metrics you define — the rubric is yours |
| Decoding effort | High — every entry needs translation and discipline research | Low — entries decode themselves; recognition replaces translation |
| Team trust | Fragile — opaque outputs breed skepticism over time | Compounding — outputs in owned language build confidence with every scan |
| Longevity | Static — the entries never learn your business | Designed for iteration — your team extends and versions it after handover |
Ready to see the full program arc? Foundations, the database phases and the private track are laid out with transparent numbers on the pricing overview.
See Programs & PricingThe TimeWaver Field Notes
Decoding insights, straight to your inbox
Occasional field notes from real trainings — decoding techniques, honest research notes, and first access to quarterly cohort seats and session openings.
By joining, you agree to receive the TimeWaver Field Notes by email. Unsubscribe anytime.
What a custom database is not
It is not a validated measurement system, and building one does not change the honest science: the scientific mainstream does not recognize Information Field theory, and studies from the manufacturer are vendor pilots. TimeWaver is used in this work as a consciousness and information-field support tool. It is not presented as a conventional diagnostic instrument or a replacement for medical, psychological, legal, or financial advice. A custom database makes the reflective lens legible to your team — it does not turn it into a laboratory instrument.
Frequently asked questions
How long does it take to build a custom TimeWaver database?
Roughly six months across two phases. Phase 2 — discovery, metric design and the version 1 build — runs about three months. Phase 3 — pilot, iteration and handover — runs about three months more. Each phase is scoped and confirmed separately, so you commit one phase at a time.
Do we need to know how to program?
No. Database entries are authored in structured natural language — your team's contribution is vocabulary, frameworks and judgment, not code. We handle the entire technical build, and the handover documentation covers everything your team needs to maintain and extend the database without engineering support.
Can the database grow after handover?
Yes — it is designed for exactly that. Version 2 ships with SOP documentation covering how to author new entries, retire stale ones, and version the database as your language evolves. Iteration by your own trained team is the intended long-term state, not an add-on.
What happens to our data and frameworks?
They remain yours. The vocabulary, frameworks, metrics and every entry authored during the build belong to your organization, and confidentiality is the default throughout the engagement. We do not reuse your material for other clients, and we never reference client work publicly.
Do we need the Foundations training first?
A trained core team is the prerequisite — and that is precisely what Foundations builds. A custom database is only as good as the team decoding it, so we build databases for organizations whose people already run and read analyses with confidence. If your team is not there yet, Foundations is the right first step.
The TimeWaver Field Notes
Before you go — take the Field Notes with you
Occasional field notes from real trainings — decoding techniques, honest research notes, and first access to quarterly cohort seats and session openings.
By joining, you agree to receive the TimeWaver Field Notes by email. Unsubscribe anytime.