work / product lineage

Built from a job,
not a feature checklist.

Scratchive's product history is a record of workflow problems explored through software. The labels below distinguish an externally linked product from historical concepts; they do not invent availability or performance figures.

products & concepts · 01

Four directions from the first chapter.

Each started with a specific operational job: communicate, confirm, recover or collect.

Product lineageWhatsApp automation

ActionSender

A campaign automation product built around bulk messaging, scheduling, contact management, integrations and AI-assisted conversations.

visit product site ↗
Historical conceptPayment event automation

Noffipay

An SMS-to-webhook/API concept for turning bank and mobile-financial-service messages into structured payment events for connected systems.

Documented as product history
Historical conceptCart recovery

Abandango

An AI-assisted abandoned-cart recovery concept designed around personalized WhatsApp follow-up for commerce workflows.

Documented as product history
Historical conceptConversational forms

ChattyFill

A conversational-form concept that turns static data collection into adaptive chat-like flows and routes clean data into operational tools.

Documented as product history

recurring patterns · 02

The reusable work behind different products.

01

Event-driven operations

Turn external signals—messages, payments, orders or form activity—into a traceable next action.

02

Human-aware automation

Automate the repeatable path while routing uncertain or sensitive cases to a person.

03

Conversation as interface

Use messaging or chat-like flows when they reduce friction without hiding structure.

04

Operational visibility

Make ownership, status, retries and exceptions legible to the people running the system.

evidence standard · 03

Real proof belongs here when it can be published.

The site intentionally excludes the legacy placeholder testimonials, generic client counter and unsupported performance claims. Approved case studies can later add the problem, delivered system, named client permission and measurable outcome.

a related problem?

The strongest starting point is your workflow, not one of these product names.

Describe the people, systems and exceptions involved. We can then tell you whether a product, integration, extension or focused custom build is the useful shape.