Loading this page.
DIRECT ANSWERS
Thirteen questions a small team should settle before adding another tool, a dashboard or an AI workflow. Each answer starts with the answer. Where the answer is that something is unfinished or unconnected, it says that instead of describing the plan for it.
It is the operating layer between a business process, the people doing the work, the evidence they produce and the decision that follows. Most businesses already own tools for each of those separately. What is usually missing is the thing that connects them: the rule about what happens next, who owns it, and what would have to be true for it to count as done.
A cube is one end-to-end, repeatable customer process, from first contact to a verified outcome. It carries the source somebody arrived through, the stages of the journey, the handoffs between them, the SOPs describing each job, the evidence each job owes, the quality checks applied to that evidence, and the measures taken from it.
A source is how a customer entered: a social platform, search, an event or a referral. A source variant changes the instructions at the front of the process without changing the process itself. A referral and a cold search enquiry arrive knowing different amounts, so they are met with different questions, and everything behind that stays comparable.
Evidence is what a job actually produced, submitted against the action rather than against a task list, with the time it took recorded beside it. What counts as evidence is written into the SOP before the work starts, not negotiated afterwards. That ordering is the whole point: a standard agreed after the result is known is not a standard.
No. A CRM can remain the system where customer records live. two7 is the rulebook around the work: what should happen next, who owns it, what proof is required and how the result is reviewed. Those are different jobs, and a business that swaps one for the other usually ends up doing neither well.
A tracker records that somebody ticked a box, and the person who did the work is usually the person who ticked it. In two7 the evidence behind a completed action is reviewed by somebody else, every required check has to pass, and a failed check returns the work rather than closing it. Completed and verified stay two different states.
No. The foundation that exists today supports assigned work, training and independent review, all of which assume people. Automation is not connected, and when it is it belongs on proven, bounded steps, after access, approvals, safe retries and failure handling have been agreed, with human review kept wherever the risk requires it.
Somebody other than the person who did it. Nobody approves their own attempt. Every required check must pass and missing proof cannot be averaged away by the checks that did pass. A failed check returns the work for rework or for focused practice, and the practice is retested on separate real work rather than on the practice attempt itself.
Not in this version. two7 authors the templates. A business installs an approved, versioned copy of one and fills the fixed setup slots it declares. There are seven lead-to-close templates with their source variants, plus supporting SOPs for hiring, finance, delivery and capacity. If the requirement is a blank canvas for arbitrary workflows, this is not that product.
Owners and Admins install templates and assign work. Managers review their own business’s work. Members see and submit their own assigned work, training and evidence, and not another member’s. A custom role subtracts from the role it is built on and never adds to it, and a draft grants nothing until a reviewed version is pinned to a named person.
There is no published price, because the work is scoped before it is quoted. What a first implementation costs depends on the process, how many people run it and what state the current documentation is in. The honest version is that a number quoted before any of that is known would be a number made up. Bring a process and the scope can be defined against it.
No. Real provider connections and webhooks are not finished, and a service that is not connected is labelled as not connected rather than shown as working. A placeholder cannot be switched on by pasting a key into it. Where a connection matters to your process, say so early, because it changes the sequence of an implementation.
Admission is invitation only until a separate public launch decision. Creating an account does not by itself grant membership of a business. In practice the route in is a conversation about one process, an agreed scope, and then an invitation into a workspace set up for it.
STILL UNSETTLED
If the question that matters to you is missing, it is probably the interesting one. Send it over and we will answer it directly, including when the answer is that we have not built that yet.
Ask two7Longer research answers →