How to Prepare Your Company for Digital Due Diligence in 90 Days

You know digital due diligence is real. You know that investors, procurement teams, and AI agents are verifying your company online. What you need now is a plan.

Not a vague "improve your online presence" recommendation. A specific, week-by-week roadmap that takes your company from wherever it is now to a state where it can survive digital due diligence at every layer. Audit, fix, build, verify. In 90 days.

I developed this roadmap from building entity infrastructure for three companies simultaneously. PT Arsindo (pump distribution), Hibrkraft (leather journals and publishing), and Witanabe (industrial engineering). Each had different starting points, different industries, different verification challenges. But the 90-day structure worked for all three because it follows the natural sequence of how verification systems process information.

The roadmap has four phases. Each phase builds on the previous one, so skipping ahead does not work.

Phase 1: The audit (weeks 1-2)

You cannot fix what you have not measured. The first two weeks are entirely dedicated to understanding your current state. No building. No fixing. Just documenting every gap.

Week 1: Digital presence inventory

Create a comprehensive list of every place your company appears online. Every single one. This includes:

• Owned properties: Your website, email domain, any subdomains or microsites.
• Social profiles: LinkedIn (company and personal), Facebook, Instagram, Twitter, YouTube, any platform where you have an account.
• Directory listings: Google Business Profile, industry directories, business databases, chamber of commerce listings, certification body databases.
• Government registries: AHU (for Indonesian companies), OSS licensing, tax registration, any regulatory filings.
• Third-party mentions: News articles, blog posts, review sites, academic citations, anywhere your company name appears that you did not create.

For each entry, document: the URL, the company name as it appears, the address listed, the key personnel named, the description provided, and the date it was last updated. I cover the full methodology for this in my essay on auditing AI visibility.

This inventory is tedious. It is also the most important step in the entire 90 days. Every subsequent action depends on knowing exactly where you stand.

Week 2: Consistency gap analysis

Take your inventory from week one and compare every entry against every other entry. What you are looking for is inconsistency. Specifically:

Name consistency. Is your company name exactly the same everywhere? Not "mostly the same." Exactly. "PT Arsindo Integrasi Pompa" is not the same as "Arsindo" or "PT. Arsindo Integrasi Pompa" (note the period after PT). Machines treat these as potentially different entities.

Address consistency. Same standard. "Jl. Raya Pajajaran No. 15" is not the same as "Jalan Pajajaran 15." Standardize to one format and use it everywhere.

Personnel consistency. If your website says "Ibrahim Anwar, Director" and your LinkedIn says "Ibrahim A., CEO," that is a gap. Title changes, name abbreviations, and role discrepancies all create verification friction.

Certification claims. Every certification mentioned on your website should be verifiable on the certifying body's database. Check. If your ISO certification expired six months ago but your website still claims it, that is not a minor inconsistency. That is a red flag.

Document every gap in a simple spreadsheet. Platform, what it says now, what it should say, priority (high/medium/low), owner, deadline. This becomes your action plan for Phase 2.

Phase 2: Foundation (weeks 3-4)

Now you fix things. The sequence matters. Start with the highest-impact, fastest fixes and work toward the more complex implementations.

Week 3: Fix inconsistencies and implement schema

Days 1-3: Fix all name, address, and personnel inconsistencies. Go through your gap analysis spreadsheet and update every platform. This is mechanical work. Logging into each platform, updating the information, saving. There is no shortcut. Some platforms have slow review processes (Google Business Profile updates can take days to verify), so start with the slowest ones first.

Days 4-7: Implement Organization schema. This is the single most impactful structural change you can make. Add JSON-LD Organization schema to your homepage with:

• Legal name and any alternate names
• Founding date
• Registration number (taxID or other identifier)
• Address (must match all other platforms exactly)
• Contact information
• Industry classification (NAICS or ISIC codes)
• Key personnel (founders, directors) with Person schema
• sameAs array linking to all verified external profiles
• Certifications with verifiable URLs

The Entity Infrastructure course walks through the implementation details for each schema element. If you do not have JSON-LD experience, this is the one step where hiring help is justified. The schema needs to be valid (test with Google's Rich Results Test) and complete. Incomplete schema is sometimes worse than no schema because it tells machines "this entity tried to declare itself but the data is partial."

The Trust Chain Methodology provides the framework for understanding which signals to prioritize. The Identity layer, your schema declarations, must be solid before you build the Evidence and Entity layers on top of it.

Week 4: Core profile optimization

LinkedIn optimization. Your company page should have: a complete description matching your website, a logo and banner image, your website URL, industry classification, company size, and headquarters location. Key personnel should have their personal profiles updated with consistent job titles and company information.

Google Business Profile. If you do not have one, create it. If you have one, make it complete. Photos (real photos of your office, team, products, not stock images), business hours, service descriptions, and most importantly, respond to every review, positive or negative. An active GBP with responses signals management attention.

Website updates. Ensure your About page lists leadership with full names (matching LinkedIn and registry), your Contact page has a physical address (matching GBP and registry), and your homepage clearly communicates what you do. Remove or update any outdated information. If a case study references a project from 2019, make sure the client still exists and the details are still accurate.

Phase 3: Corroboration (weeks 5-8)

Phase 2 built the foundation. Phase 3 builds the verification network that corroborates your foundation. This is the phase most companies skip, and it is why most companies fail layers 2 and 3 of digital due diligence.

Weeks 5-6: Directory and registry updates

Identify the three to five most important directories for your industry. Not every directory. The ones that verification teams actually check. For industrial companies in Indonesia, this typically includes: your industry association directory, government procurement databases (LPSE/SIKaP), and international platforms like Kompass or ThomasNet if you serve export markets.

For each directory, ensure your listing is:

• Active and current (not a forgotten profile from 2018)
• Complete (all fields filled, not just the required ones)
• Consistent with your website and schema (exact same name, address, personnel)
• Categorized correctly (right industry codes, right service descriptions)

Simultaneously, verify your government registry data. In Indonesia, check your AHU listing, OSS license status, and any sector-specific registrations. If anything is outdated or incorrect, start the update process now. Government systems are slow. Starting in week 5 gives you enough buffer to have clean data by the end of the 90 days.

Weeks 7-8: Third-party signals and Wikidata

Third-party verification signals. This is the corroboration layer that makes your entity machine-verifiable. As I discuss in the essay on making infrastructure visible to auditors, the key is having your claims confirmed by sources you do not control.

Actions for this phase:

• If you have client relationships that can be publicly referenced, get them documented. A testimonial on the client's website is more valuable than one on yours. A joint case study published by both parties is strongest.
• If you have certification relationships, ensure the certifying body's database shows your current status. Contact them if it does not.
• If you have industry association memberships, ensure your membership is listed in their public directory.
• If you have press coverage, ensure those articles are still live and indexed by search engines.

Wikidata submission. If your company has enough notability (press coverage, institutional clients, government relationships, published works), submit a Wikidata entry. Wikidata is the knowledge base that feeds Google's Knowledge Graph and is consulted by AI agents. A Wikidata entry with proper references significantly increases your chances of getting a Knowledge Panel and being accurately described by AI systems.

The review process takes 2-4 weeks, which is why you start it in week 7 rather than week 12. Rejection is common on the first attempt. Build in time for revision and resubmission.

Phase 4: Verification (weeks 9-12)

The final phase is testing and remediation. You built the infrastructure. Now verify that it works.

Week 9-10: AI agent testing

Ask multiple AI agents about your company and key personnel. Use ChatGPT, Gemini, Perplexity, and any other AI agent you can access. Ask specific questions:

• "What is [company name]?"
• "Who is the founder of [company name]?"
• "Is [company name] ISO certified?"
• "What industry does [company name] operate in?"
• "Where is [company name] located?"

Document the responses. Are they accurate? Are they complete? Do they cite your website or third-party sources? Are there errors? AI responses reflect the quality of your entity infrastructure. Errors in AI responses indicate gaps in your verification network that need to be addressed.

Important caveat: AI training data has lag. Changes you made in weeks 3-8 may not be reflected in AI responses yet. That is expected. The question is whether your infrastructure is correctly structured so that future training data updates will capture accurate information.

Week 11: Cross-reference audit

Go back to your week 1 inventory and repeat the consistency check. Every platform, every listing, every profile. Has everything been updated correctly? Have any platforms reverted or been overwritten? Are there new listings you did not know about?

Run Google's Rich Results Test on your homepage. Verify that your Organization schema is still valid and complete. Check that your sameAs links resolve correctly. Test your Google Business Profile status. Verify your Wikidata entry (if submitted) has been reviewed and published.

This audit often reveals issues that were missed or that emerged during the implementation process. A directory listing that was updated in week 5 might have been "corrected" by the platform's automated systems. A GBP edit might still be in review. These need attention.

Week 12: Final gap remediation

Address anything that the week 11 audit revealed. Prioritize by impact: inconsistencies that affect the company name or key facts first, secondary details second.

At the end of week 12, you should have:

• A complete digital presence inventory with all entries consistent
• Valid Organization schema with verifiable attributes on your website
• Active, complete profiles on LinkedIn, Google Business Profile, and key industry directories
• Consistent data across government registries
• Third-party corroboration signals (client references, certification verification, directory listings)
• A Wikidata entry (submitted, if not yet published)
• AI agent verification that produces accurate results (or infrastructure in place for accurate future results)

What this roadmap does not cover

This is a 90-day preparation plan, not a long-term digital strategy. It does not cover:

Content marketing. Publishing essays, white papers, or case studies is valuable for entity authority, but it is a continuous activity, not a 90-day project. The roadmap gets your structural infrastructure right. Content builds on top of that over months and years.

Press and media outreach. Getting press coverage is important for corroboration, but it is unpredictable and cannot be scheduled into a week-by-week plan. What the roadmap does is ensure that any existing press coverage is properly indexed and that your infrastructure is ready to capitalize on future coverage.

Ongoing monitoring. Entity infrastructure requires maintenance. Platforms change, registry data expires, certifications renew. After the initial 90-day build, you need a quarterly review process to keep everything current. I typically recommend a light audit every 90 days and a full audit annually.

For companies in Southeast Asia, the 90-day timeline is particularly relevant because the competitive landscape is shifting fast. Companies that build entity infrastructure now establish a verification advantage that compounds over time. Companies that wait will find the bar has risen by the time they start.

Resource requirements

The 90-day roadmap requires approximately:

Internal time: 40-60 hours of work spread across the 90 days. This includes the audit (10-15 hours), fixing inconsistencies (5-10 hours), profile updates (10-15 hours), and testing (10-15 hours). Most of this is mechanical, not creative. It does not require senior leadership time except for decisions about what information to disclose and what claims to make.

External cost: $500-$2,000 if you hire help for schema implementation and technical SEO. $0 if your team has JSON-LD experience. Directory listings are usually free for basic profiles. Some premium directories charge $200-$500/year.

Elapsed time: 90 days minimum due to external processing times (GBP verification, Wikidata review, Knowledge Graph indexing). The actual work could be done faster, but the external dependencies create a floor.

Compare this to the cost of failing digital due diligence once on a $200,000 contract. The math is not close.

The entity infrastructure service compresses this timeline by handling the technical implementation, but the audit and verification phases still require company participation because only you know your business well enough to validate accuracy.