Intakit Sites
With Intakit Sites, discovery, direct intake, DONNA preparation, response, and conversion visibility become one connected client journey—so public attention turns into prepared action instead of disappearing between vendors.
The website stops being a marketing island and becomes the public edge of firm intelligence.
A conventional website stops at the form. Intakit Sites begins an approval-gated firm workflow, then gives the firm evidence to improve what happens next.
One client journey. Separate public and private systems. Approved public facts and content can be published for people, search engines, and AI assistants. Intake, clients, matters, documents, billing, and firm sessions remain behind the protected Intakit boundary. Privileged matter data never enters the public Sites runtime.
Keep the existing CMS or agency-managed site as the live source of truth. Connected Foundation links the public experience to protected Intakit intake and portal journeys, with endpoint monitoring at the handoff; deeper delivery and connector work activates only when proven for the firm’s CMS.
Operate the public website beside the protected Intakit platform on a separately deployed public-only runtime. Native connects site inquiries directly to firm workflows, gives approved firm knowledge an approval-gated publishing path, and keeps privileged legal work outside the website runtime.
Albaugh staging proof · July 10, 2026
The exact QA-host browser gate found zero failed redirects, unresolved internal links, or failed public assets and measured 100% minimum normalized coverage of the imported website content. This is staging evidence for the migrated content—not a ranking guarantee or the final customer-domain launch certificate.
When Native is the right choice, Intakit builds beside the live site, measures what must be preserved, and keeps public DNS unchanged until the customer’s evidence packet is green.
See the evidence-gated migration process or read the preservation covenant.
Controlled early access: Native Sites is in controlled release with Albaugh as the first proof migration. The isolated runtime and evidence system are proven on the QA domain; a customer-domain launch is accepted only when that customer’s route, security, analytics, and rollback packet is green.
Migration pricing is based on canonical content routes, not generated archives or documented redirects. The signed Authority & AI Visibility Report locks the tier, evidence sources, exclusions, review rounds, and custom requirements.
It is one evidence-based deliverable: your complete URL inventory and site health, how your titles, metadata, and structured data present your practice today, where you appear — and don't — in live search results for the buyer-intent queries that matter, and how AI answer engines can read and cite your firm today. Every finding quotes the actual evidence and discloses exactly which engines and queries were checked. Any provider-API sample is labeled as such; it does not query ChatGPT web, Perplexity, Google AI Overviews, or the consumer Claude and Gemini apps. The report ends with a concrete migration recommendation, and the $750 fee is credited to an accepted migration within 90 days. It is a diagnosis with receipts, never a ranking guarantee.
No. Connected mode keeps the external CMS or agency-managed site as the live source of truth. Native mode moves the public website to Intakit. Both use the same approval, evidence, and attribution standard; tenant isolation applies to Intakit-controlled data and connector surfaces, while the external CMS remains controlled by its owner and hosting provider.
No responsible migration provider can guarantee a search-engine outcome. Intakit’s production launch covenant requires the agreed URL inventory, documented route outcomes, rendered metadata and content comparison, protected-journey and analytics proof, rollback rehearsal, and post-launch monitoring to be green before customer DNS moves.
No. DONNA can draft and assemble evidence, but a human with Site Publisher authority must approve every public revision before activation or connector delivery.
Native is sold with an exit covenant: the firm keeps its domain and approved content, and production activation requires a proven export of content, assets, route and redirect manifests, metadata, and publication history. Export is a launch control, not an after-the-fact promise.
The Authority & AI Visibility Report is delivered within two business days after complete access. Essentials and Focused migrations normally produce a working preview in one to two business days and become launch-ready within five business days after Review approval. Content-rich migrations such as Albaugh normally produce a preview in two to three business days and target launch-ready within ten business days. Custom sites are scoped individually. Customer approvals, missing evidence exports, third-party credentials, and DNS windows pause the clock. Hypercare continues for 30 days after launch.
Often, yes, once complete source access exists. A first automated import and working preview may be produced in one business day. We do not call it launch-ready until route inventory, visual and factual approval, protected-journey and analytics proof, accessibility and performance checks, and rollback are complete. Productized delivery is measured in business days—not months.
Native recurring billing begins when the customer-domain site launches. Customer or vendor delay after an accepted preview is handled under the signed migration scope or a written change order; it does not silently start the website subscription early. Migration and recurring Sites access remain separate value units.
Native can remove the recurring hosting, CMS maintenance, plugin, security, backup, and form-integration layer. It does not include unlimited copywriting, photography, campaigns, backlink outreach, or unrelated custom applications.
Often, when it replaces verified spending on hosting, CMS and plugin maintenance, security and backups, form integration, and recurring technical remediation. The Authority & AI Visibility Report records what the firm pays today and distinguishes costs that disappear, costs that remain, and capabilities that move into Intakit. We do not compare the full Enterprise operating-platform subscription to website hosting alone; the Native decision is based on verified avoidable spend, operational risk removed, and integration gained.
No. Native Sites runs in a separate public-only service with no Intakit session, client, matter, document, billing, or AI-provider access. Secure intake and portal journeys open the protected Intakit origin by normal HTTPS navigation; the public site does not receive privileged cookies or broad cross-origin API access.
Your public domain stays yours and points to the isolated Sites service only after route, TLS, analytics, and rollback evidence is green. Your protected Intakit app remains a separate origin with its own host-scoped session security. Email and unrelated DNS records are inventoried and left untouched during the website cutover.