ARK and Clearframe are built for people who need the work to stay organized after the first conversation. This page explains what you get, what you provide, what happens next, and what stays private.
Probably both, eventually. The website is what people see when they find you. The system is what keeps the work organized after they reach out. Most businesses start with the website and add the system once they realize how much time they spend chasing information they should already have.
Yes. You do not need to know how any of it works behind the scenes. You describe what you need. You get back something that works. The technical side stays on this end.
Clearframe builds the thing people see: your website, intake forms, and proof of work. ARK runs what is behind it: memory, records, automations, and the logic that keeps work moving after someone reaches out.
Yes. ARK can work alongside what you already have. The starting point is getting your important information organized so future work does not have to start from zero.
Yes. ARK is useful for anyone building something over time who keeps losing the thread: decisions made in one session, scattered notes, or the same context re-explained every time someone new gets involved.
It is a memory setup. You provide the important information about your project, business, or work. It gets organized into one record that future sessions, tools, and handoffs can all start from.
It is a mapping session for something new. You share what you know and what you need. It comes back as a clear map: what this is, who it is for, what you have, what you need, where the edges are, and what to do first.
It is a security check for your public files. Obelisk looks for things that should not be visible, then tells you what was found, how serious it is, and what to do about it.
Automations are repeat work that runs on a schedule instead of requiring you to do it manually: posts, reports, file sorting, intake routing, or other recurring tasks.
Ongoing support. Instead of a one-time setup, the system keeps improving with small fixes, new automations, and adjustments as the work changes.
You reach out and describe what you are dealing with: what you are building, what is not working, and what you need sorted. The right starting point gets identified from there.
It depends on the work. For memory setup, share what you do, what matters, what your services or offers are, what you have decided, and what is currently happening. Rough information is fine.
A private intake starts. Nothing sensitive goes through public forms. You share details through a private channel, and you receive the finished result in a form you can keep, review, and use.
A one-time setup usually completes within a few business days after everything needed is received. Custom automation builds depend on scope and get quoted with a timeline.
Continuum delivers a clean memory record. Genesis delivers a structured brief and first-action plan. Obelisk delivers a plain-language report. Automations deliver a working tool and instructions. Clearframe sites deliver a live website with the needed pieces connected.
The information you share is used to do the work you asked for. It is not shared with third parties, used to train anything, or exposed publicly.
Anything you mark as private stays private. Part of setup is defining what can be referenced in future work and what must stay off-limits.
No. Anything that affects something sensitive, such as a payment, published post, or customer message, requires your sign-off first.
The record is meant to stay current. You can update what is included, what is off-limits, or what the rules are as the work changes.
Not immediately. The initial setup gives you something useful from day one. Over time, the record should be updated when your offer, rules, or services change.
That is what Operator support is for. One-time setups handle the starting point. Ongoing work handles new automations, updates, expanded coverage, and new tools.
Reach out. Every setup includes a clear record of what was built and how, which makes finding and fixing problems faster than starting from scratch.
Yes. Each project gets its own record and setup. They do not share information or bleed into each other.
A website that does the job it is there to do. At minimum: a clear offer, proof of past work, and a way for people to reach you or request something. From there it can include forms, uploads, galleries, review pages, saved records, and more.
Information about your business: what you do, who you serve, how pricing works, examples of your work, and how you want people to reach you. You do not need polished copy or design direction.
A straightforward service site can be done in one to two weeks. More complex builds with backend tools, dashboards, or integrations take longer and get scoped individually.
The site is live and yours. Ongoing changes can be handled through support or quoted individually. If ARK is connected, those pieces are maintained under the plan that covers the ARK work.
Yes. ARK can connect to an existing site. It does not require rebuilding what you already have.
Start with Continuum. It gives you one organized record that each future session can start from.
Start with Genesis. Share what you know, even if it is messy, and get back a structured map and first-action path.
Start with Obelisk. Share the site or files before launch and get a report on what to fix before it becomes a problem.
That is an automation candidate. Describe the task, inputs, and definition of done. A tool can be built around that routine.
That is the full Clearframe plus ARK build. The site handles what people see. ARK handles what runs behind it.
That is fine. Describe what is not working or what you are trying to do. The right starting point gets identified from that.
You do not need the perfect brief. Bring the project, business, files, questions, or repeated task. The first job is turning that into a usable starting point.
