Things you can ask your website for

Three of the most requested. They all work the same way: circle the area where you want something to happen, with your mouse or your finger, write the sentence, and that's it. What changes from case to case is what you say.

A form that receives drawings

A form field can be a file, and that changes what you can ask. Up to 100 MB per file, so it makes no difference whether it's a photo, a thirty-page PDF or an audio clip.

A tattoo artist asks for the sketch and quotes without anyone coming in.
A phone repair shop asks for a photo of the broken screen.
A print shop lists its prices and adds a place to drop the PDF. No more walking in with a USB stick.
A guitar teacher asks for a clip of you playing, and knows your level before the first lesson.
A bakery asks for a photo of the cake you liked, instead of hoping you can describe it.
A vet asks for a photo of the wound and tells you whether to run over or whether it can wait.

Replies are stored in your panel, your phone gets a ping the moment someone writes, and the files download from there.

A video, without the cookie banner

Anyone can put up a video. What almost nobody tells you is the consequence: an embedded video loads things from its home site, and that puts a third party's cookies on your website even if we add none ourselves. From that moment on, your site needs the cookie banner.

That's why you ask for it the way the video shows: nothing loads until someone presses play. The thumbnail shows, nothing external loads, and whoever wants to watch it clicks.

The same trick works for anything embeddable: a song, a map, a booking calendar.

Knowing what visitors actually do

Visits count themselves from day one. What almost nobody has is the other thing: knowing what visitors do. You can measure up to forty different things on the same site.

And there are no cookies here. A unique visitor is a fingerprint computed with the day's salt and thrown away: the same person, on the same day, on your site, counts once. Tomorrow the salt changes and that fingerprint is worthless, so nobody can be followed from one day to the next or across two sites. The IP address goes into the calculation and is stored nowhere.

What you lose with that, we'll say plainly: we don't know whether Tuesday's visitor is the same one who came back on Thursday. What you gain is a website that never has to ask permission for anything, because there is nothing to permit.

And others almost nobody thinks to ask for

Today's chalkboard. Send a photo of the bar's chalkboard from your phone and the menu on the site updates itself.
Knowing which product people want before you make it. Put up the three you're considering, measure which gets pressed most, and make that one.
The button that doesn't work. Measure how many people reach the form and how many send it. If a hundred arrive and three send it, the problem isn't the website.
A CV inbox that accepts the PDF and pings your phone, instead of an address that fills up with spam.
A waiting list for an event, with the sign-up counter in plain sight so people can tell it's filling up.
Your latest single playing on your page, with the dates below and an inbox to hear about the next one.
Measuring what time people visit, and moving your opening hours to when they actually look for you.

None of this takes more than an afternoon

There's no panel to learn and nobody to phone to change a number. You tell us what you do, we build the groundwork, and from then on the site is yours.

Get in on day one

Thought of something that isn't here? Write to hola@taraceista.com and we'll tell you if it can be done. A person answers.