Part 3 — Foundations stage of the loop
3.1 Action selection rationale for cycle 1
The practitioner selects actions for the first engagement cycle based on AS-finding diagnosis and capacity considerations.
| Action | Rationale |
|---|---|
| O-1 (Competitive Analysis) | Establish competitive context; identify the AI-mediated competitive set (which may differ from the CMO’s stated competitive set) |
| O-2 (Analytics & KPI Framework) | Establish reporting infrastructure; define KPIs that connect AS-VS to commercial outcomes |
| O-4 (Technical Infrastructure) | The most foundational action; addresses crawler access (currently fine), performance (currently acceptable), and the URL/canonicalization architecture that will be needed for subsequent work |
| O-5 (Structured Data Foundation) | Implement Organization schema, Product schema, Article schema across the site; address the V1.1 floor |
| M-1 (Question-Based Opportunity Mapping) | Identify what questions Avela’s prospects ask about workforce planning; substrate for subsequent M-pillar work |
Five parallel actions; the practitioner notes this is at the upper bound of what Avela’s capacity supports. The actions are split across teams: O-4 and O-5 are engineering work; O-1, O-2, M-1 are analytical/practitioner work that doesn’t require Avela’s internal capacity.
The CMO asks why Generative-pillar work isn’t included in cycle 1. The practitioner explains:
“Generative-pillar work has hard prerequisites that aren’t yet in place. G-11 Wikipedia work requires entity verification (G-1) plus 3-5 substantive third-party citations from Wikipedia-reliable sources — Avela has earned media but most of it is in trade publications that Wikipedia editors evaluate carefully. G-4 media outreach requires citation-worthy content (G-3) — Avela’s existing content is product-marketing rather than reference-grade. G-9 academic citations require depth content plus methodology-defensible original research — neither exists. We can begin Generative-pillar foundations through G-1 in cycle 2 once O-5 is complete and the entity scaffolding is in place. Substantial G-pillar work will follow over multiple cycles.”
The CMO accepts this with mild reluctance. The practitioner notes the reluctance for ongoing relationship management — this is the kind of stakeholder pressure that, if not addressed honestly, leads to premature G-pillar attempts that fail.
3.2 What gets done in the foundations stage
The foundations-stage work spans multiple cycles. The work in summary:
Cycle 1:
- O-1, O-2, M-1, M-5 baseline (analytical work)
- O-4 technical foundation work (Avela engineering)
- O-5 entity-schema and content-type-schema implementation (Avela engineering with practitioner support)
Cycle 2:
- O-3 internal E-E-A-T signals (Avela editorial + engineering)
- O-6 content audit (practitioner-led, informs Avela editorial)
- O-7 compliance and trust infrastructure (Avela legal + editorial)
- M-2 answer-first content architecture beginning (Avela editorial)
- G-1 entity verification (practitioner + Avela)
Cycle 3:
- M-3 dedicated FAQ and knowledge hubs beginning (Avela editorial + practitioner)
- M-6 evidence-based content discipline establishment (Avela editorial)
- M-8 content refresh and decay management (Avela editorial)
- O-pillar maintenance discipline established
- G-1 expansion to additional knowledge-graph systems
The work is substantial across cycles. The CMO notices the rhythm: each cycle has three or four large action streams plus smaller maintenance work. The work spans multiple Avela teams; coordination across teams is part of the practitioner’s role.
3.3 What we expect to see and what we don’t
Through the foundations stage, the expected patterns:
What we expect to see:
- AS lifting noticeably from cycle 1 to cycle 2 to cycle 3
- The lift is concentrated in Optimize pillar initially (V1.1 specifically), then expanding to Manifest pillar (V2.1 and V2.2) by cycle 3
- Generative pillar moves slowly because foundational G-1 work is in cycle 2-3 and external citations don’t appear until subsequent cycles
- Recognition gate clearing on at least one platform by cycle 2 or 3
- Initial navigational-tier VS signal emerging by cycle 3
What we don’t expect to see:
- Headline AS jumping from Critical to Strong in foundations stage; Strong band is authority-stage territory
- Substantial advisory-tier VS movement; that’s depth-into-authority-stage signal
- VS consistently catching up to AS within cycle; lag is expected
- Linear improvement; some cycles show concentrated lift, others show stable AS with under-the-surface preparatory work
3.4 First re-measurement: reading the result
After cycle 1’s work substantially completes, the AS re-measurement produces:
| Dimension | Cycle 1 baseline | Cycle 1 result | Movement |
|---|---|---|---|
| Headline AS | 14 | 23 | +9 |
| Optimize pillar | 22 | 38 | +16 |
| Manifest pillar | 15 | 16 | +1 |
| Generative pillar | 6 | 7 | +1 |
| VS | 3 | 4 | +1 |
| Recognition gate | Block | Block | No change |
The reading:
“AS lifted from 14 to 23. Most of the lift came from Optimize pillar — V1.1 moved from 8 to 28 as the structured-data foundation came in; V1.2 moved from 36 to 48 as O-4 work tightened the technical infrastructure. Manifest barely moved because we haven’t done substantive M-pillar editorial work yet — M-1 is analytical and doesn’t lift datapoints directly. Generative barely moved because we haven’t started G-pillar work yet. This is the expected foundations-cycle-1 pattern.
VS hasn’t moved meaningfully. Recognition gate is still blocking. We’d expect to see the first recognition signals in cycle 2 or 3 as platforms ingest the structured-data foundation we put in place. The lag between AS lift and VS lift is structural; this isn’t a problem.”
The CMO’s response: “So the work worked. When does this start showing up in AI?”
The practitioner: “We’re still 6-12 weeks from when we’d expect the structured-data work to be ingested by the major platforms. Some platforms will show it earlier; some will be slower. We’ll measure VS each month and look for the first signs.”
3.5 What the loop has revealed about the brand
After the first three cycles of foundations work, the AS measurement looks substantially different:
| Dimension | Engagement start | After cycle 3 | Movement |
|---|---|---|---|
| Headline AS | 14 | 38 | +24 |
| Optimize pillar | 22 | 64 | +42 |
| Manifest pillar | 15 | 32 | +17 |
| Generative pillar | 6 | 18 | +12 |
| VS | 3 | 11 | +8 |
| Recognition gate | Block | Warn (cleared on 2 of 4 platforms) | Improvement |
The practitioner walks the CMO through what the loop has revealed:
“Avela has moved from Critical band into the lower part of the Developing band. The Optimize pillar is now in the high Developing range, reflecting completed foundations work. Manifest is in low Developing — we’ve started the work but the substantive M-pillar lift is depth-stage work that compounds over more cycles. Generative is still in low Developing because the work we’ve done so far is foundations (entity verification, knowledge-graph beginning) rather than the citation-earning work that produces V3.1 lift.
Recognition gate has cleared on two of four major AI platforms; on those, we’re starting to see navigational-tier signal. The remaining two platforms will likely follow as their training cycles refresh.
Importantly, the loop has revealed something we should plan around: Avela’s Generative-pillar work is going to require sustained external focus. The brand has thin earned-media presence, no Wikipedia, no Wikidata, and no original research. The Generative-pillar lift will require a multi-cycle commitment to G-3, G-4, G-8, and eventually G-11. We can plan that commitment now or wait until the depth-stage work surfaces it again — my recommendation is to plan it now.”
The CMO agrees. Cycle 4 will begin depth-stage work explicitly while continuing Generative-pillar foundations.
3.6 Stage-transition signal
By the end of cycle 3, multiple foundations-to-depth transition signals are present:
- AS has lifted from Critical band into low-to-mid Developing band sustainably
- Optimize pillar has reached a maintenance plateau in the high Developing range
- Recognition gate has substantially cleared on at least one major platform
- The CMO is asking content-strategy questions rather than infrastructure questions
- The action selection conversation has shifted from “what’s broken” to “what should we deepen”
The transition isn’t sharp; cycle 4 will continue some foundations-stage work alongside depth-stage initiation. But the brand has moved through the transition.
3.7 Cross-industry cameo: Foundations stage in regional hospitality
A regional hospitality brand — call it Pulau Heritage Resorts, a boutique hotel group operating six properties in Indonesia and Malaysia — engages Avonetiq from a similar AS ≈ 0 starting state. The structural patterns of foundations-stage work are nearly identical to Avela’s, despite the brand operating in a different industry, geography, and language scope.
| Stage element | Avela (B2B SaaS) | Pulau Heritage (regional hospitality) |
|---|---|---|
| Headline AS at start | 14 (Critical) | 11 (Critical) |
| Pillar bottleneck | Generative at 6 (floor) | Generative at 5 (floor) |
| Foundations action priority | O-5 structured data | O-5 structured data + O-7 compliance (regional regulatory) |
| Capacity constraint | Communications | Both communications and editorial |
| First measurable AS lift | Optimize pillar | Optimize pillar |
| First measurable VS signal | Navigational tier on 2 of 4 platforms | Navigational tier on 1 of 3 measured platforms |
The structural pattern is the same: foundations work lifts Optimize first, Manifest second, Generative third. The headline AS moves from Critical to Developing. Recognition gate clears progressively. Operational specifics differ — Pulau Heritage’s structured-data work emphasizes LocalBusiness, Hotel, and Place schemas rather than Organization and Product; their O-7 work involves regional regulatory compliance (UU PDP for Indonesian operations, plus Malaysian equivalents) that Avela doesn’t face; their multilingual scope is more complex (English, Indonesian, plus Traditional Chinese for the Singaporean weekend traveler segment) than Avela’s English-only scope.
But the discipline is the same. The diagnostic conversation runs on the same structural logic. The action sequencing follows the same prerequisite chains. The expected pattern of AS-VS divergence in foundations stage shows up identically. The recognition gate clears as foundations work is ingested.
This is what cross-industry generalization means in practice: surface details vary; the structural patterns are stable.
Bagian 3 — Tahap Foundations dari loop
3.1 Dasar pemilihan action untuk siklus 1
Praktisi memilih action untuk siklus engagement pertama berdasarkan diagnosis temuan AS dan pertimbangan kapasitas.
| Action | Dasar Pemilihan |
|---|---|
| O-1 (Competitive Analysis) | Membangun konteks kompetitif; mengidentifikasi competitive set yang dimediasi AI (yang mungkin berbeda dari competitive set yang disebutkan oleh CMO) |
| O-2 (Analytics & KPI Framework) | Membangun infrastruktur pelaporan; mendefinisikan KPI yang menghubungkan AS-VS dengan hasil komersial |
| O-4 (Technical Infrastructure) | Action yang paling mendasar; menangani akses crawler (saat ini baik), performa (saat ini dapat diterima), serta arsitektur URL/kanonikalisasi yang akan dibutuhkan untuk pekerjaan selanjutnya |
| O-5 (Structured Data Foundation) | Mengimplementasikan Organization schema, Product schema, Article schema di seluruh situs; mengatasi floor V1.1 |
| M-1 (Question-Based Opportunity Mapping) | Mengidentifikasi pertanyaan yang diajukan calon klien Avela seputar workforce planning; substrat untuk pekerjaan M-pillar selanjutnya |
Lima action paralel; praktisi mencatat bahwa ini berada di batas atas dari kapasitas yang dapat didukung Avela. Action-action tersebut dibagi antar tim: O-4 dan O-5 merupakan pekerjaan rekayasa; O-1, O-2, M-1 adalah pekerjaan analitis/praktisi yang tidak memerlukan kapasitas internal Avela.
CMO bertanya mengapa pekerjaan Generative-pillar tidak dimasukkan dalam siklus 1. Praktisi menjelaskan:
“Pekerjaan Generative-pillar memiliki prasyarat ketat yang belum terpenuhi. Pekerjaan Wikipedia G-11 memerlukan verifikasi entitas (G-1) ditambah 3-5 kutipan substantif dari pihak ketiga yang berasal dari sumber yang diakui reliabel oleh Wikipedia — Avela memiliki earned media namun sebagian besar berasal dari publikasi perdagangan yang dievaluasi secara cermat oleh editor Wikipedia. G-4 media outreach memerlukan konten yang layak dikutip (G-3) — konten Avela yang ada saat ini bersifat product-marketing, bukan bermutu referensi. G-9 kutipan akademis memerlukan konten mendalam ditambah riset orisinal yang dapat dipertahankan secara metodologi — keduanya belum ada. Kita dapat memulai fondasi Generative-pillar melalui G-1 di siklus 2 setelah O-5 selesai dan scaffolding entitas telah tersedia. Pekerjaan G-pillar yang substansial akan menyusul dalam beberapa siklus berikutnya.”
CMO menerima penjelasan ini dengan sedikit keengganan. Praktisi mencatat keengganan tersebut untuk pengelolaan hubungan yang berkelanjutan — inilah jenis tekanan stakeholder yang, bila tidak ditangani secara jujur, dapat berujung pada upaya G-pillar prematur yang berakhir gagal.
3.2 Apa yang dikerjakan pada tahap Foundations
Pekerjaan pada tahap Foundations mencakup beberapa siklus. Ringkasan pekerjaan:
Siklus 1:
- O-1, O-2, M-1, M-5 baseline (pekerjaan analitis)
- O-4 pekerjaan fondasi teknis (rekayasa Avela)
- O-5 implementasi entity-schema dan content-type-schema (rekayasa Avela dengan dukungan praktisi)
Siklus 2:
- O-3 sinyal E-E-A-T internal (editorial + rekayasa Avela)
- O-6 audit konten (dipimpin praktisi, memberikan informasi bagi editorial Avela)
- O-7 infrastruktur kepatuhan dan kepercayaan (legal + editorial Avela)
- M-2 permulaan arsitektur konten answer-first (editorial Avela)
- G-1 verifikasi entitas (praktisi + Avela)
Siklus 3:
- M-3 permulaan FAQ khusus dan knowledge hub (editorial Avela + praktisi)
- M-6 penetapan disiplin konten berbasis bukti (editorial Avela)
- M-8 pembaruan konten dan manajemen peluruhan (editorial Avela)
- Disiplin pemeliharaan O-pillar ditetapkan
- G-1 perluasan ke sistem knowledge-graph tambahan
Pekerjaan ini cukup substansial di seluruh siklus. CMO memperhatikan ritmenya: setiap siklus memiliki tiga atau empat alur action besar ditambah pekerjaan pemeliharaan yang lebih kecil. Pekerjaan ini mencakup beberapa tim Avela; koordinasi antar tim merupakan bagian dari peran praktisi.
3.3 Apa yang diharapkan terjadi dan apa yang tidak
Sepanjang tahap Foundations, pola yang diharapkan:
Yang kami harapkan terjadi:
- AS naik secara terlihat dari siklus 1 ke siklus 2 ke siklus 3
- Kenaikan terkonsentrasi pada Optimize pillar awalnya (khususnya V1.1), kemudian meluas ke Manifest pillar (V2.1 dan V2.2) pada siklus 3
- Generative pillar bergerak lambat karena pekerjaan G-1 yang mendasar berada di siklus 2-3 dan kutipan eksternal belum muncul hingga siklus-siklus berikutnya
- Recognition gate terbuka pada setidaknya satu platform pada siklus 2 atau 3
- Sinyal VS tier navigasional awal mulai muncul pada siklus 3
Yang kami tidak harapkan terjadi:
- AS headline melompat dari Critical ke Strong pada tahap Foundations; band Strong adalah wilayah tahap authority
- Pergerakan VS tier advisory yang substansial; itu adalah sinyal jauh ke dalam tahap authority
- VS secara konsisten mengejar AS dalam satu siklus; kelambatan memang diharapkan
- Peningkatan linier; beberapa siklus menunjukkan kenaikan terkonsentrasi, siklus lain menunjukkan AS yang stabil dengan pekerjaan persiapan yang berlangsung di bawah permukaan
3.4 Pengukuran ulang pertama: membaca hasilnya
Setelah pekerjaan siklus 1 sebagian besar selesai, pengukuran ulang AS menghasilkan:
| Dimensi | Baseline siklus 1 | Hasil siklus 1 | Pergerakan |
|---|---|---|---|
| AS headline | 14 | 23 | +9 |
| Optimize pillar | 22 | 38 | +16 |
| Manifest pillar | 15 | 16 | +1 |
| Generative pillar | 6 | 7 | +1 |
| VS | 3 | 4 | +1 |
| Recognition gate | Block | Block | Tidak ada perubahan |
Pembacaan hasil:
“AS naik dari 14 ke 23. Sebagian besar kenaikan berasal dari Optimize pillar — V1.1 bergerak dari 8 ke 28 seiring masuknya fondasi structured-data; V1.2 bergerak dari 36 ke 48 seiring pekerjaan O-4 memperketat infrastruktur teknis. Manifest hampir tidak bergerak karena kami belum melakukan pekerjaan editorial M-pillar yang substansial — M-1 bersifat analitis dan tidak mengangkat datapoints secara langsung. Generative hampir tidak bergerak karena kami belum memulai pekerjaan G-pillar. Ini adalah pola yang diharapkan pada foundations-cycle-1.
VS belum bergerak secara berarti. Recognition gate masih memblokir. Kami berharap melihat sinyal recognition pertama di siklus 2 atau 3 saat platform-platform mencerna fondasi structured-data yang telah kami pasang. Kelambatan antara kenaikan AS dan kenaikan VS bersifat struktural; ini bukan masalah.”
Respons CMO: “Jadi pekerjaan ini berhasil. Kapan ini mulai terlihat di AI?”
Praktisi: “Kita masih 6-12 minggu lagi dari saat yang kami harapkan pekerjaan structured-data akan dicerna oleh platform-platform utama. Beberapa platform akan menampilkannya lebih awal; beberapa akan lebih lambat. Kami akan mengukur VS setiap bulan dan mencari tanda-tanda pertamanya.”
3.5 Apa yang telah diungkapkan loop tentang brand ini
Setelah tiga siklus pertama pekerjaan Foundations, pengukuran AS terlihat jauh berbeda:
| Dimensi | Awal engagement | Setelah siklus 3 | Pergerakan |
|---|---|---|---|
| AS headline | 14 | 38 | +24 |
| Optimize pillar | 22 | 64 | +42 |
| Manifest pillar | 15 | 32 | +17 |
| Generative pillar | 6 | 18 | +12 |
| VS | 3 | 11 | +8 |
| Recognition gate | Block | Warn (terbuka di 2 dari 4 platform) | Peningkatan |
Praktisi memandu CMO melalui apa yang telah diungkapkan loop:
“Avela telah bergerak dari band Critical ke bagian bawah band Developing. Optimize pillar kini berada di kisaran Developing tinggi, mencerminkan pekerjaan Foundations yang telah selesai. Manifest berada di Developing rendah — pekerjaan sudah dimulai tetapi kenaikan M-pillar yang substansial adalah pekerjaan tahap depth yang bertumpuk selama beberapa siklus. Generative masih di Developing rendah karena pekerjaan yang telah kami lakukan sejauh ini adalah foundations (verifikasi entitas, awal knowledge-graph) bukan pekerjaan penghasil kutipan yang menghasilkan kenaikan V3.1.
Recognition gate telah terbuka di dua dari empat platform AI utama; pada keduanya, kami mulai melihat sinyal tier navigasional. Dua platform yang tersisa kemungkinan akan mengikuti saat siklus pelatihan mereka diperbarui.
Yang penting, loop telah mengungkapkan sesuatu yang perlu kita rencanakan: pekerjaan Generative-pillar Avela akan memerlukan fokus eksternal yang berkelanjutan. Brand ini memiliki kehadiran earned-media yang tipis, tidak ada Wikipedia, tidak ada Wikidata, dan tidak ada riset orisinal. Kenaikan Generative-pillar akan memerlukan komitmen multi-siklus pada G-3, G-4, G-8, dan pada akhirnya G-11. Kita dapat merencanakan komitmen itu sekarang atau menunggu hingga pekerjaan tahap depth memunculkannya kembali — rekomendasi saya adalah merencanakannya sekarang.”
CMO setuju. Siklus 4 akan memulai pekerjaan tahap depth secara eksplisit sambil melanjutkan Generative-pillar Foundations.
3.6 Sinyal transisi tahap
Pada akhir siklus 3, beberapa sinyal transisi foundations-ke-depth telah hadir:
- AS telah naik secara berkelanjutan dari band Critical ke band Developing rendah-hingga-menengah
- Optimize pillar telah mencapai plateau pemeliharaan di kisaran Developing tinggi
- Recognition gate telah terbuka secara substansial pada setidaknya satu platform utama
- CMO mengajukan pertanyaan seputar strategi konten, bukan pertanyaan infrastruktur
- Percakapan pemilihan action telah bergeser dari “apa yang rusak” menjadi “apa yang perlu kita perdalam”
Transisi ini tidak tajam; siklus 4 akan melanjutkan sebagian pekerjaan tahap Foundations bersama inisiasi tahap depth. Namun brand ini telah melewati transisi tersebut.
3.7 Cameo lintas industri: tahap Foundations pada hospitaliti regional
Sebuah brand hospitaliti regional — sebut saja Pulau Heritage Resorts, sebuah kelompok hotel butik yang mengoperasikan enam properti di Indonesia dan Malaysia — menjalin engagement dengan Avonetiq dari titik awal AS ≈ 0 yang serupa. Pola struktural pekerjaan tahap Foundations hampir identik dengan Avela, meskipun brand ini beroperasi di industri, geografi, dan cakupan bahasa yang berbeda.
| Elemen tahap | Avela (B2B SaaS) | Pulau Heritage (hospitaliti regional) |
|---|---|---|
| AS headline di awal | 14 (Critical) | 11 (Critical) |
| Bottleneck pillar | Generative di angka 6 (floor) | Generative di angka 5 (floor) |
| Prioritas action Foundations | O-5 structured data | O-5 structured data + O-7 compliance (regulasi regional) |
| Kendala kapasitas | Komunikasi | Komunikasi dan editorial |
| Kenaikan AS pertama yang terukur | Optimize pillar | Optimize pillar |
| Sinyal VS pertama yang terukur | Tier navigasional di 2 dari 4 platform | Tier navigasional di 1 dari 3 platform yang diukur |
Pola strukturalnya sama: pekerjaan Foundations mengangkat Optimize terlebih dahulu, Manifest kedua, Generative ketiga. AS headline bergerak dari Critical ke Developing. Recognition gate terbuka secara bertahap. Spesifikasi operasional berbeda — pekerjaan structured-data Pulau Heritage menekankan skema LocalBusiness, Hotel, dan Place, bukan Organization dan Product; pekerjaan O-7 mereka melibatkan kepatuhan regulasi regional (UU PDP untuk operasi di Indonesia, ditambah padanannya di Malaysia) yang tidak dihadapi Avela; cakupan multibahasa mereka lebih kompleks (Inggris, Indonesia, ditambah Mandarin Tradisional untuk segmen wisatawan akhir pekan dari Singapura) dibandingkan cakupan bahasa Inggris saja milik Avela.
Namun disiplinnya sama. Percakapan diagnostik berjalan dengan logika struktural yang sama. Urutan action mengikuti rantai prasyarat yang sama. Pola divergensi AS-VS yang diharapkan pada tahap Foundations muncul secara identik. Recognition gate terbuka seiring pekerjaan Foundations dicerna.
Inilah makna generalisasi lintas industri dalam praktik: detail permukaan berbeda-beda; pola strukturalnya stabil.