Skip to content

AI that does the work
and shows its sources.

AI development services that ship real work: chatbots that answer from your own documents, automation that clears the repetitive queue, knowledge systems that cite every answer. Built on the stack you already run, with a working pilot and no black boxes: you see the prompts, the evaluation results and the source behind every answer.

Reply within four business hours (typical) · No platform lock-in

Brands our teams have delivered for

  • Hello Peter
  • Gruber Logistics
  • Delhivery
  • Thomson Reuters
  • Qatar Airways
  • Grundfos
  • Save
  • BERD
  • Yale University
  • Kuwait Police
  • Dubai Police
  • Panasonic
  • Infosys
  • Kia
  • Hitachi
  • Orange Business Services
What we do

PixelCrayons builds AI chatbots, workflow automation, knowledge systems and personalisation on your existing stack. Every engagement starts with a scoped pilot: one workflow, your own data, a working deliverable. Guardrails, evaluation and handover are included, answers show their sources, and anything that shouldn't run unsupervised keeps a person in the loop. We work direct for brands and white-label for agencies.

  1. Discovery & scoping, in writingOne workflow mapped, its data audited and a correct result defined before anything is built.
  2. Built on your stackBuilt on the cloud, CRM and helpdesk you already run, with models you can swap.
  3. Guardrails & evaluationAn evaluation suite from your real cases, grounding checks and a human handover when uncertain.
Selected work

Judge the work,
not the adjectives.

Outcomes tied to real engagements, not averages.

All case studies →
Where the work happens
ShopifyWooCommerceMagentoWordPressWebflowKlaviyoGoogle AdsMeta AdsGA4Next.js
  • Reply within four business hours (typical)
  • Clear IP & Ownership Terms
  • Grounded answers: sources shown
  • Human handover built into every assistant
  • Your stack: no forced migration
  • Delivering since 2004, before and after the AI wave
Pick your starting point

Every way in.
One senior team.

Most engagements start with a single pilot (a chatbot, an automation, a knowledge base) and grow once it has earned its keep. The pilot is chosen for a measurable queue or question volume, so its value is visible before anything larger is scoped.

Looking to be cited by ChatGPT, not to build with it?

That is a different job: structuring your site so answer engines can quote it, with sources pointing back to your pages. It needs content, schema and authority work rather than a model or a pipeline, which is why it lives under marketing, where one published SaaS case earned AI Overview citations alongside 127% organic traffic growth (single engagement).

In every engagement

What an AI build
actually includes.

01

Discovery & scoping, in writing

We map the one workflow worth automating first, audit the data and systems it touches, and define what a correct result looks like, before anything is built. Discovery also answers the question most vendors skip: whether you should build at all. The pilot scope you approve is small enough to prove value in weeks and itemised enough to hold us to.

Week zero
02

Built on your stack

No forced platform migration. We build on the cloud, CRM and helpdesk you already run, and choose models on fit, cost and data residency, structured so the model underneath can be swapped without rework when better or cheaper options ship. Which they do, every few months.

Every build
03

Guardrails & evaluation

Every assistant ships with an evaluation suite built from your real cases: grounding checks against your documentation, uncertainty thresholds that trigger a human handover instead of a guess, and logs you can audit after the fact. If it doesn't know, it says so. An assistant that guesses in front of a customer costs you more trust than any number of correct answers earn back.

Before launch
04

Integration with existing systems

The pilot plugs into the tools your team already lives in (helpdesk, CRM, Slack, internal APIs) so adoption never depends on anyone changing how they work. If a system has no API, we find the seam; that's the craft part of the job.

Included
05

Handover & training

Documentation, admin training and a runbook your own team can operate without us, including how to update the knowledge base, read the evaluation reports and adjust the escalation rules. Your materials remain yours. Bespoke deliverable rights, licences and handover are agreed before work starts. No lock-in, no black box, no dependency on us to keep the lights on.

At handover
How it starts

A working deliverable,
not a slide deck.

01
Start

Brief and a call

We sign an NDA and talk through the workflow worth automating first and the documents and systems it touches.

02
Once the brief is complete

Itemised proposal

We confirm the date your proposal arrives. It covers one workflow, real data, named guardrails, a demo date and the itemised price.

03
Your decision

You sign off

You confirm the scope, the payment and the access we need. Nothing starts before this.

04
Typically 2 to 3 business days later

The team starts

We audit the documents and systems the workflow touches and agree in writing what a correct result looks like.

05
On the date in your proposal

First deliverable

A working pilot grounded in your own documents. It then runs against real cases, integrates with your helpdesk and CRM, and your team is trained on the runbook.

Inside Prism

Your engagement, week to week,
in one workspace.

Prism is the client workspace where your requests, approvals, tasks and weekly reviews live.

Where the engagement includes it, your AI build runs in a Prism workspace you log into: requests, approvals, the task list and the weekly review, with each decision and its expected result written down.

  • 01

    Requests and approvals, in one place

    Raise a request in your workspace, approve a piece of work, and see who owns it and when it is due.

  • 02

    Owned tasks and routines

    Every task has one owner and a date. Recurring work runs as a routine, so nothing depends on someone remembering.

  • 03

    A weekly review with decisions recorded

    Each decision is written down with the expectation attached: what we expect to change, and by when.

  • 04

    Every action recorded, checked against the outcome

    What we did and what happened sit side by side, so the next review starts from evidence rather than memory.

How we report it, in Prism

The eval scorecard,
before the pilot goes near a customer.

What you receive in month one

AI work is reported against an evaluation set built before any model is chosen. In the first month you receive the task definition with the inputs and acceptable outputs written down, the eval set of real cases with expected answers, and the scorecard showing accuracy, refusal behaviour and cost per run. The go/no-go checklist names what must hold before the pilot touches live traffic.

  • 01Task definition: inputs, acceptable outputs, and the cases the system must decline
  • 02Eval set: real cases with expected answers, reviewed by your team
  • 03Scorecard: accuracy, refusal behaviour, latency and cost per run
  • 04Go/no-go checklist: the thresholds the pilot must meet before launch
  • 05Failure log: each wrong answer, its cause, and the fix applied

Related workB2B SaaS: from invisible to answer-engine cited.SaaS · UK · A different discipline, so it is linked here rather than presented as proof of this one.

Beyond AI

One senior team, four disciplines.

The chatbot, the site it lives on and the search visibility that feeds it are built by one team on one roadmap. Agencies resell all of it white-label.

Who is accountable

The people accountable
for the work.

Leadership and how we’re built →
Parvessh Agarwal

Parvessh Agarwal

Founder & CEO

An entrepreneur at heart who connects business analysis, strategy, clear objectives and ROI with practical technology solutions.

LinkedIn →
Saundaraya Gupta

Saundaraya Gupta

Technical Manager

Brings technical delivery, client communication and project management together so work moves from brief to release smoothly.

LinkedIn →

Every engagement

A named coordinator and escalation contact

Know who coordinates your engagement, who owns the work and how to escalate an issue.

All engagements. Roles may be combined and vary with your engagement.

Full terms →
Before you sign

Our commitments

Each one says where it applies and links to its full terms.

Response and start times

We typically respond within four business hours. Eligible engagements can typically start within two to three business days after scope, payment and required access are confirmed.

Business hours are Monday to Friday, 9:00 am to 6:00 pm IST, excluding published company holidays. Typical expectations, not guaranteed service levels.

Full terms

Clear IP & Ownership Terms

Your materials remain yours. Bespoke deliverable rights, licences and handover are agreed before work starts.

All engagements.

Full terms

Clear Delivery & Escalation Ownership

Know who coordinates your engagement, who owns the work and how to escalate an issue.

All engagements. Roles may be combined and vary with your engagement.

Full terms

How we handle claims, credentials and your data: group credentials, dated ratings, how case figures are signed off, client permissions and data handling.

What discovery decides

Buy a tool, build a pilot,
or keep a person on it.

Discovery ends with a written recommendation, and sometimes it says not to build. These are the findings that decide which way it goes.

What discovery findsWhat we recommendWhy
The workflow is generic and an off-the-shelf tool can already reach your dataSubscribe to the tool, and the document says soA pilot that should not exist wastes your money and our reputation.
The workflow is core to how you make moneyA scoped pilot: one workflow, your own data, a working deliverableThis is where custom earns its keep, and the pilot proves it before anything larger is priced.
Answers must come from your own documentationA grounded build that shows its sourcesEach answer can be checked against the passage it came from, and low confidence hands over instead of guessing.
The ready-made option cannot connect to the systems your team usesCustom, built on your existing cloud, CRM and helpdeskAdoption should never depend on anyone changing how they work. If a system has no API, we find the seam.
A step needs a judgement call, such as a refund outside the returns windowAutomate around it and route that step to a personThe assistant passes on the full thread and the relevant policy. It does not make the call.
Your data must not leave your infrastructureDeploy inside your own cloud account or private environmentRetention, residency and access rules are agreed in the scope document, not discovered after launch.

Scaling beyond the pilot is priced only after the pilot has earned it.

Questions

Frequently
asked.

Less than most agencies imply, because we start with a scoped pilot: one workflow, your data, a working deliverable. The proposal itemises what ships, including the integrations, guardrails, evaluation and handover. Scaling beyond the pilot is priced only after the pilot has earned it.

The ones that fit your data, budget and residency requirements, decided in discovery. We're model-agnostic, and builds are structured so the model can be swapped without rework as better or cheaper options ship. What matters more is how answers are grounded, how failures are caught and how the system plugs into the tools and cloud you already run.

It stays yours. Work runs under NDA, and your documents and customer data ground your system and nothing else. Where needed we deploy inside your own cloud or private environment, on enterprise API terms under which providers don't train on your data. Retention, residency and access rules are agreed in the scope, and access is logged.

Any language model can, so our job is to make errors rare, visible and safe. Every assistant answers from your own documentation with sources shown, and when confidence is low it hands over to a human. It's tested against your real cases before launch, and the logs let you audit what was said and why.

Sometimes buy, and we'll tell you so in discovery. Off-the-shelf makes sense when the workflow is generic and the tool can reach your data. Custom earns its keep when the workflow is core to how you make money, answers must come from your documentation, or no tool integrates with your systems. Discovery ends with a written recommendation either way.

Whoever you choose: you're not locked to us. Every build hands over with documentation, admin training and a runbook your team can operate, under IP and ownership terms agreed before work starts. A light retainer for monitoring, evaluation re-runs and changes is the usual shape, itemised in writing and cancellable, or you run it in-house.

A working pilot, not a slide deck: one workflow, your own data and a working deliverable, built on the stack you already run. Guardrails, an evaluation suite from your real cases and a runbook for your team are included. Your materials remain yours, with deliverable rights, licences and handover agreed before work starts.

The range

What it costs,
at the direct rate.

Each AI service is priced on its own row below as a pilot and a retainer; the team is for buyers with a roadmap across several of them who want one standing senior team, billed monthly.

  • RetainerAI engineering team$4K–$16Kper month

Indicative: every figure is refined into an itemised proposal.INR figures shown excl. GST.

Put AI to work on
one real workflow.

Scope a pilot: one workflow, your own data, a working deliverable with guardrails, evaluation and handover included, and a written recommendation if custom isn't the right call.

Reply within four business hours (typical) · NDA standard · Clear IP & Ownership Terms

Last updated