Question 1

How is this different from a dev shop?

Accepted Answer

A dev shop builds what you spec and hands it back. We design the agent, build it, and run it in production, with a check on every action and a person in the loop where it counts. The difference shows up after launch, because we are still there.

Question 2

How is this different from the Big 4?

Accepted Answer

Senior people do the work and the price is agreed for the result before we start. What you are left holding at the end is a running system.

Question 3

How does pricing work?

Accepted Answer

Three stages. Discovery is a fixed fee, then a one-off to design and build it, then a monthly to run, watch and improve it. The first call is complimentary and you leave it knowing the discovery fee. Build and run are quoted off what discovery finds, so you know what each stage costs before it starts.

Question 4

What does the first call cost?

Accepted Answer

It is complimentary. We work out whether there is a job here worth doing, and you leave with the discovery fee in front of you, so you can decide with the number in hand.

Question 5

What does an engagement look like?

Accepted Answer

Discovery first, where we work out what is worth building and what it is worth. Then we build the agent and the working memory it runs on, holding your data, rules and decisions. Then we run it on a monthly retainer, improving it as your rules change.

Question 6

How long does discovery take?

Accepted Answer

Two to three weeks for most teams. It ends with a map of the job, the case for automating it, and a fixed price for the build. Discovery gives you the call in plain words, whichever way it goes.

Question 7

If the agent makes a call you would not have made, what happens?

Accepted Answer

Out-of-policy actions are flagged, held or blocked before they run, and a person clears anything that needs judgement. During Run we watch the system in production, and the audit trail records exactly what happened and why, so nothing gets papered over.

Question 8

Can we stop the Run stage?

Accepted Answer

Run is a monthly arrangement. If the numbers stop working, you can walk away.

Question 9

Who owns what you build?

Accepted Answer

You do. The agents, the system they run on, your data and rules inside it, and the audit history: all of it stays yours, whether or not we keep running it.

Question 10

What systems do you work with?

Accepted Answer

Whatever runs your business today: your accounting stack, your CRM, spreadsheets, email, the lot. Agents act through the same systems your team uses, on their own accounts, so you can always see which actions were theirs.

Question 11

How do you keep our data safe?

Accepted Answer

Access is scoped to the job, nothing sensitive leaves your systems without a rule that allows it, and every action leaves an audit trail recording who did what and when. Sensitive moves wait for sign-off. Data residency is written into the rules the agent cannot cross. Fydis is the layer that enforces it.

Approach.

Discovery

Build

Run

Common questions.

Start with one job.

Approach.

Discovery

Build

Run

Common questions.

Q1How is this different from a dev shop?

Q2How is this different from the Big 4?

Q3How does pricing work?

Q4What does the first call cost?

Q5What does an engagement look like?

Q6How long does discovery take?

Q7If the agent makes a call you would not have made, what happens?

Q8Can we stop the Run stage?

Q9Who owns what you build?

Q10What systems do you work with?

Q11How do you keep our data safe?

Start with one job.