Free exploration
Free access is useful for trying the workflow and deciding where thinQit fits in your team.
The mental model of thinQit
Understand the core thinQit vocabulary: Codex, Compass, Teammates, Cody, projects, credits, workspaces, and the build loop.
Core ideaContext plus execution
Primary layersCodex, Compass, Teammates
Useful forShared vocabulary
Mental model
One loop, three surfaces
thinQit is easier to use once the nouns are clear. Codex builds, Compass remembers, and Teammates execute role-specific work. Together, they give your team one workspace for turning ideas into artifacts and keeping the context connected.
The loopPreserve
Stage 01 - Preserve
Compass preserves context
Compass organizes knowledge into pages and constellations so decisions, goals, research, and dependencies stay readable after the chat moves on.
think - build - ship - improve, one connected loop
Workspace model
Projects, pages, teammates, and settings live together
The workspace is where projects, pages, teammates, people, settings, billing, and connected tools come together. It keeps product work, context, and follow-up from becoming scattered.
Landing pageready
Pitch deckdraft
Launch planlinked
SEO notespublished
SophiaSEO
Masonsupport
Integrations4 active
Team8 seats
Vocabulary
Make the nouns easy to remember
Use this glossary to understand Codex, Compass, Cody, teammates, projects, pages, credits, and artifacts without slowing down your first session.
CodexBuild layer
Where ideas become product artifacts: websites, web apps, wireframes, presentations, bug fixes, and implementation changes.
CYCodyBuilder teammate
thinQit's builder teammate helps scope work, ask clarifying questions, create artifacts, and keep implementation connected to context.
PRProjectsBuild artifacts
Project artifacts live in Codex. Common starting points include websites, web apps, wireframes, and presentations.
CRCreditsUsage capacity
Credits represent usage capacity for AI-powered work. Exact plan limits live in the billing page in your workspace.
CompassContext layer
Knowledge organized into connected pages and constellations so decisions, goals, research, and dependencies stay readable.
TeammatesSpecialist agents
Role-specific AI operators with workflows, setup, tools, and task surfaces. They execute against context, not only answer questions.
PGPagesCompass knowledge
Pages live in Compass. They describe product areas, research, support knowledge, launch plans, decisions, and open questions.
ARArtifactsConcrete output
The concrete output of a session: a page, app screen, wireframe, presentation, checklist, audit, plan, or teammate task result.
Cody
Cody is the builder teammate inside the product
Cody is thinQit's builder teammate. Cody helps scope work, ask clarifying questions, create artifacts, and keep implementation connected to the product context.
Credits
Credits represent usage capacity, not product value
Credits represent usage capacity for AI-powered work. Exact plan limits and top-up options can change by plan, so use the billing page in your workspace as the source of truth.
Paid plans
Paid plans add more capacity for serious build work, shared workspaces, and teammate workflows.
Top-ups
Top-ups, when available, add extra usage without changing the whole workspace plan.
Build pipeline
The platform loop is think, build, ship, then improve
thinQit's product story repeats across the site: define the outcome, build the artifact, preserve context, delegate specialist work, and feed results back into the workspace.
Capture goals, constraints, product context, and decisions in a form the team can reuse.
Use Codex and Cody to create or change the artifact with reviewable evidence.
Use teammates and humans to handle SEO, security, support, docs, QA, and operational readiness.
FAQ
Common questions
Is Compass just documents?
No. Compass treats knowledge as connected pages in a cosmos. The links and relationships are part of the product, not decoration.
Are Teammates just chatbots?
No. Teammates are role-specific operators with workflows, setup, tools, and task surfaces. They should execute against context, not only answer questions.
What is the difference between Cody and Codex?
Codex is the build workspace. Cody is the developer teammate who helps scope, implement, and iterate inside that workspace.
What is an artifact?
An artifact is the concrete output of a work session: a page, app screen, wireframe, presentation, checklist, audit, plan, or teammate task result.
Why does Compass matter if I already have chat history?
Chat history is useful for replaying a conversation. Compass is for reusable product knowledge: decisions, links, launch context, open questions, and pages that future work can reference directly.