A model of your business.
Customers act inside a wider context: accounts, orders, products, projects. maxclicks represents people as contacts, business entities as objects and actions as events. Typed attributes define their fields. Relationships connect the records without flattening everything onto a customer profile.
REST and CSV bring records into the workspace. Your source systems keep that context current.
Answers beyond stored fields.
An evaluated attribute defines a question once and evaluates it from the relevant records when used. It can calculate a value, such as a customer’s spend in a period, or find related records, such as their latest order.
The audience might use a purchase count. The message can use the selected order and product details. A count tells you who qualifies; the related records help explain what to say.
From a requirement to a reviewable rule.
maxinja turns a plain-language requirement into logic for supported attributes, campaign conditions and workflow steps. You can inspect the definition and matching records before using the result.
Relationships preserve the distinction that matters. Two people can belong to the same account while having different project histories. A teammate’s project should not count as the recipient’s own progress.
Personal writing inside a fixed design.
Adaptyle generates instructed subject or body regions as each recipient’s email is prepared for delivery. It uses the selected customer context and brand guidance. The design, links and wording outside those regions remain authored.
Liquid inserts supplied values, such as a name, price or URL. Adaptyle writes the passages that need interpretation. Preview representative recipients and review the writing against the records before sending.
One goal, connected work.
maxinja coordinates specialists across the data model, audience, email and workflow. Refine the same campaign in conversation, inspect the resulting work and choose when to schedule or publish it.
A journey checks what changed.
An event can start a configured workflow. After a wait, Query reads current records. Conditions determine the next branch; an AI step can return structured guidance for a later action. A newer purchase or completed project can stop an outdated follow-up.
Broadcasts prepare a campaign for an audience. Workflows send within a journey. Applications call saved templates through REST or SMTP. Sender configuration and the message’s marketing or transactional setting determine the applicable delivery checks.
What stays under your control.
You define the source data, inspect the audience and journey, choose the writing instructions and keep exact facts in authored or Liquid regions. Agents connect the work; the campaign remains available to review and refine.