Raccog started with a small, annoying observation: the slowest part of putting something on the internet has nothing to do with the thing itself. A café that wants a website spends its week choosing a platform.
So we built the shortcut we wanted — say what the business is, get a real website back, change what is wrong, publish it. The first version wrote a single page. It now builds every page a site needs, keeps a version at each change, and puts the whole thing on your own domain.
Then people started asking it for things that were not marketing pages at all — an orders dashboard, a booking form, a docs section, the sign-in screen in front of a tool. So the builder learned to tell those apart. It classifies the request first and builds to that kind: a sidebar and a sortable table for a dashboard, the form in the first viewport for a contact page, plans before anything decorative for pricing.
The same engine grew a second half. Once a model can read a brief and write working output, it can also read an invoice, an inbox or a support queue — so we build those automations too, for teams who have a bottleneck rather than a website.