Marketing brings people in and captures contacts

Know what brought each person, and keep their contact.

A blog and a page that show how far each one was read, with no cookie. One link per post, to know which one brought each click. A form that delivers every response. And a newsletter from your domain, only for people who asked for it.

Same login in every dashboard. A code arrives in your email; you paste it once. The dashboard is in Portuguese for now.

Where to start

What is missing to bring people in?

Pick the sentence that is yours. The piece that solves it is under it.

Pages

I want a page with my links.

Build your link-in-bio page. In Pages, it goes live and shows which button each person tapped.

See Pages

Links

I need a QR code I can change later.

In Links, the printed QR code points to a destination you change whenever you want.

See Links

Decks

I am going to present an idea.

Turn your text into slides. In Decks, the deck comes out with your brand.

See Decks

Stores

I want to sell what I make.

In Stores, your product with its price becomes your store.

See Stores

Still choosing? Start with the line's guides (in Portuguese)

AI for making slides: a whole presentation from one sentence
A Canva alternative in Portuguese: Brazilian templates and your brand
Gamma app: what it is, and a Brazilian option with your brand
A blog on your domain: subdomain or /blog, and what changes for SEO
A conversion page in blocks: how to build a landing page that measures itself
A newsletter only for people who confirmed: why double opt-in matters
See all the guides on the blog (in Portuguese)

The proof

This line runs on the house's own pieces.

It is not a showcase. It is Ciro's own operation, right here. If a piece breaks, it breaks for him first.

This site

Published by Hoster, from the Infrastructure line.

Ciro's contact form

Received by Forms, from the Marketing line.

The line's blog

Published on Blogs, from the Marketing line.

The dashboard login

A code by email through Auth, from the Infrastructure line.

Ciro's newsletters

Sent by Newsletter, from the Marketing line, only to people who confirmed.

Ciro's agents

They work in Assistant, from the Agents line, and ask for his yes before anything that cannot be undone.

On the same line

From the First Reader to the Saved Contact

Each one handles one part of bringing people in and capturing the contact, and each one works on its own, without requiring the others.

For the agent

The Agent Does. You Decide.

Each product has an MCP server, and each tool has a rule written on the server, including what stays with a person.

The agent writes, publishes and schedules with your role on the blog. You sign it.

In Blogs, the agent reads the blog, writes the draft, and publishes or schedules only if you can publish on that blog. Taking a post down or deleting it waits for your yes, in the conversation.

The agent builds and publishes. Taking it down needs you.

In Pages, the agent creates the page, suggests text for a block, checks the destinations and publishes. Taking it down or deleting it waits for your yes, in the conversation, and the published version says who built it.

The agent fills in. Only the person consents.

In Forms, the agent creates, changes and publishes the form, and sends a response marked "by agent", never with consent. Deleting a response waits for your yes, in the conversation.

The agent creates and changes the link. Deleting needs you.

In Links, the agent does what the dashboard does: creates one link per piece, changes the destination and reads the funnel. Deactivating or deleting a link that is already circulating waits for your yes, in the conversation.

The agent writes and schedules. Deleting someone needs you.

In Newsletter, the agent you connect does what the dashboard does: writes, tests, schedules and subscribes people with proof. Unsubscribing or deleting a person waits for your yes, in the conversation.

The agent generates, edits and exports. Deleting needs you.

In Decks, the agent generates the deck, edits a card, asks the Agent, exports and opens the link to whoever you want; every AI edit leaves a version to go back to. Deleting a deck waits for your yes, in the conversation.

The first result

Sign In, Put It Out, Check

There is no discovery call. The path to the first number is the same in every product.

01

Sign in with a code

No password to create. A code arrives in your email. You paste it once, and the session works in every dashboard of the line.

02

Put it where people are

The post at /blog on your site, the campaign page, the form in one line, the short link in your bio, the newsletter signup box, the meeting deck. Or paste the prompt into your agent, and it writes the draft for you.

03

Check

The post shows up to which section it was read. The page shows each block and each button. The link shows the clicks, with previews apart. The form and the newsletter show who responded and who clicked. The deck shows how long each card was read.

Plugs into what you have

It Goes Into What You Already Have

What each product takes in from outside and sends out, and the login they share.

The site you already have

The blog goes in at /blog on your site, and everything else keeps going where it went. The form goes into any page with one line, without breaking your CSS. Without a site, the blog, the page and the form have an address on the line.

The tools you already use

The page embeds the form, the video and the checkout from any tool, and checks every 6 hours that they still respond. The short link goes wherever you want, with the UTM when the destination is your site.

Wherever you want

Blogs, Pages, Forms, Links and Newsletter send signed events in the Standard Webhooks format, to your CRM, a spreadsheet or an automation, with an outbox and retries: the post published, the broken destination, the response, the click.

What already happens in your tools

Blogs receives the permission of someone who bought, to open a locked post. Links receives visit, goal, person and purchase to close the campaign funnel. Newsletter receives consent from a form.

Same login, authorization per product.

One account signs in to Blogs, Pages, Forms, Links, Newsletter and Decks. Each dashboard shows only what is yours: another account's resource responds as if it did not exist.

Runs on Infrastructure

The line runs on Infrastructure, the way your app would: the same pieces, no shortcut. Newsletter sends through Messages, which is one of them.

The Questions, in the Order They Come Up

Marketing brings people in and captures contacts.

The whole line already works with your agent: each product speaks MCP, with four light tools that do everything the dashboard does. Deleting waits for your yes.