Wiki › Support
Refunds
Annual plans are refunded for the unused months if they're cancelled within the first 90 days; after that they run to the end of the term. Refunds over $2,000 need a second approver.
We set up Claude or ChatGPT for your company, connect it to your documents and meetings, and automate the work your team repeats every week. Where your knowledge must stay in Georgia, or your teams use more than one AI, CoDNA gives them one company memory to share.
Book a 30-minute call How a project runs
Not ready for a call? Read the free guide, Setting up Claude or ChatGPT for your company.
Also in Georgian: ქართულად
Nino, in Claude
Do we refund annual plans if someone cancels in month two?
Yes, for the unused months, as long as it's within the first 90 days.
From wiki:support/refunds
Giorgi, in ChatGPT
A customer on an annual plan wants to leave after seven weeks. Do they get money back?
Yes. Seven weeks is inside the 90 days, so refund the months they haven't used.
From wiki:support/refunds
Wiki › Support
Refunds
Annual plans are refunded for the unused months if they're cancelled within the first 90 days; after that they run to the end of the term. Refunds over $2,000 need a second approver.
Claude or ChatGPT, and Claude Code or Codex for engineers, signed in with your company accounts, connected to your documents and tools, with rules for who may use what.
CoDNA, with what you keep in Confluence, Notion or Google Drive brought in. Every AI tool reads the same pages, and each person's AI sees only what that person can see.
Two or three recurring tasks automated on the AI you already use: meeting notes turned into decisions, weekly reports, answers to the questions people keep asking. A person approves each result.
Short sessions on your own work, and two to four champions from your team who can build the next automation without us.
Eight weeks. You sign off each step as it ends, and from week three they overlap, so people learn on the automations they will use.
Discover, week 1. We talk to five to eight of your people, map the work that repeats, and agree three goals with their starting numbers.
Set up, weeks 2 and 3. Your AI tools signed in with your company accounts, and CoDNA with your documents where you need it.
Train, weeks 3 to 6. Short sessions by role, on your own work, and champions picked from your team.
Automate, weeks 4 to 7. The workflows you chose, built with your champions, each one measured.
Hand over, week 8. A results report against the starting numbers, a runbook for each automation, and your AI use policy.
Each has a fixed price, agreed before we start. If you go on within two months, what you paid counts toward the next step. We take on one new company at a time.
One day on your team's real work. We build one real change with you, and end the day deciding together whether a pilot is worth running.
Three weeks. One team and one workflow, judged on one measure we agree at the start, with a go or no-go report at the end.
Eight weeks, across your teams: two or three workflows automated, training by role, and a results report against where you started.
Tornike Razmadze, who builds CoDNA, leads each project. We follow every Claude and ChatGPT release, and teach your team what's worth using.
We work this way ourselves: CoDNA is built with Claude Code reading a CoDNA of the project's own decisions, and Medspace keeps its company knowledge in CoDNA too. Contracts are with Radium 2023 LLC in Tbilisi.
CoDNA is a company knowledge base that Claude, ChatGPT, Claude Code and Codex connect to. People keep working in the AI tool they like; the knowledge stays in one place you own.
Tell us what your team does and where the time goes. We'll tell you honestly whether AI will help, and where to start. The call is free.
Book a 30-minute call Ask about CoDNA
Not ready for a call? See the questions people ask us, or get the monthly briefing on what changes in Claude and ChatGPT.