I connect Claude to the tools you already run — your docs, your CRM, your inbox, your database — and hand over working automation with source code and a runbook. Three packages, prices listed below. You pick one, fill in a form, and I build. No sales calls, no negotiation, no scope creep.
Every package ends the same way: a working automation running against your systems, the full source repository, and documentation your team can operate without me. The price is the price.
$750fixed
One Claude integration wired into one system you already use.
Example: a RAG assistant over your company docs, answering questions inside Slack or your helpdesk.
$1,850fixed
An n8n + Claude workflow spanning two to four systems, built to fail safely.
Example: inbound email → Claude classification → CRM update → notification, with a human approving before anything is written.
$3,500fixed
A complete pipeline, end to end: ingestion, processing, validated output, delivery.
Example: PDF-to-structured-data extraction feeding your database, or a CRM automation covering intake through follow-up.
If your project doesn’t fit any package, I’ll say so after reading your intake form and we part ways cleanly — no upsell, no “custom quote.” Scope is confirmed in writing before any work or payment happens.
The whole process runs in writing. You never have to book a call, and I never ask you to.
The three packages and prices are listed above. That’s the whole price list — there is no negotiation step because there is nothing to negotiate.
Ten questions about your systems, your data, and what “working” means to you. Fifteen minutes, roughly. The questions are listed below so you can prepare answers first.
Within two business days you get a written scope document: what will be built, what is explicitly out, what access I need, and the acceptance check for day 14. Work starts only after you approve it. If your project doesn’t fit the package, I tell you that instead.
Fourteen calendar days from approved scope: the working automation, the source repository, and the runbook. You run the acceptance check from the scope doc against the live build.
Questions during the build are handled over email, in writing, with answers you can search later. If you want ongoing cover after handover, add Keep-Alive.
This is a new practice, so instead of testimonials there are two public demo repositories. Each one is a working, documented build in the same style you’d receive — read the code and judge for yourself.
A retrieval-augmented assistant over a sample company document set. It answers questions with citations back to the source documents, and when a conversation surfaces a concrete request, it writes a structured, schema-validated summary onto the matching CRM contact record. This is the shape of the $750 package.
# answer with citations, grounded in retrieved chunks resp = client.messages.create( model="claude-sonnet-5", max_tokens=1024, system=CITE_SOURCES_PROMPT, messages=[{"role": "user", "content": build_prompt(query, chunks)}], )
An n8n workflow that takes inbound documents from a webhook, has Claude extract structured fields, validates the result, and then stops for a human. Nothing is written to the destination until a person clicks approve. Rejected or failed items land in a dead-letter path with the error attached. This is the shape of the $1,850 package.
Pick your package inside the form. You’ll get a written scope document within two business days — work and payment happen only after you approve it.
No form to fight with — the intake runs by email.
Copy the ten questions on the right into an email, answer them in plain language, and send. You’ll get a written scope document within two business days — work and payment happen only after you approve it.
Send your answers to these ten questions to hello@kelsonworks.com — same process, same two-business-day scope turnaround.