The first build
Connect an agreed enquiry source, organise the request, prepare a response and notify the person reviewing it.
Automation / One useful workflow at a time
Less chasing.
Less chasing.
More following through.
Connect the steps that get missed when you are busy. Enquiries, follow-ups, review requests and repeat admin, built around the tools you already use.
You can start here with your existing website.
One enquiry, a clear next stepExample
02 / Prepared for review
“Thanks for getting in touch. I’ve got the details of your request…”
Draft only · waiting for you03 / You take it from here.
Review, edit and decide what goes out.
Illustrative example. No message is sent by this demo.
Start with one repeat job
Approval where it matters
Clear handover
Custom workflows you own
A small workflow, explainedFrom “new enquiry”
From “new enquiry”
to “ready for review”.
A 15-second example of the first few steps. Your tools and approval points are scoped around your business.
Illustrative scene and example interface. Captions are included; sound is not needed.
- 01An enquiry arrives.
A website form captures the request and contact details.
- 02The details stay together.
A record keeps the request and its next action visible.
- 03A draft is ready to review.
Business context helps prepare a response for the owner.
- 04You decide what goes out.
Check the details, edit the reply and take the conversation forward.
Already have a website? Start with the follow-up. We’ll check how your current form can connect.
Discuss my enquiry workflowWhat we would scope firstOne enquiry source.
One enquiry source.
One useful workflow.
Start small enough to understand, review and use. Add more when the first part is working.
Tell me where enquiries arrive ↗What we need from you
Your enquiry source, connected tools, business information, response preferences and the person who approves replies.
What your proposal confirms
The exact steps, approval method, testing, access, handover, setup price and ongoing tool or support costs.
Where the scope ends
Booking, quoting, CRM migration and further follow-up are separate work unless included in your proposal.
Explore the possibilities
What keeps slipping
What keeps slipping
through the cracks?
Choose a problem to see how the steps could connect. These examples are starting points for your scope.
Enquiry follow-up
Make the first reply easier.
For businesses where enquiries arrive while you are busy doing the work. Capture the details and prepare the next action in one flow.
-
01
Enquiry arrives
A form, inbox or another agreed source starts the workflow.
-
02
Details are captured
The enquiry is recorded and routed to the right place.
-
03
A reply is prepared
Use your business information to draft a response for review.
-
04
You stay in control
Approve the reply and see the next action. Booking can be scoped separately.
Example workflow. Sources, approval rules and integrations are agreed for each build.
Discuss this workflow
Past-client follow-up
Give old conversations a useful next step.
For past clients and suitable contacts you have permission to follow up. Start with a small, relevant group and a reason to get in touch.
-
01
Choose the audience
Agree on eligible contacts, the reason to reconnect and exclusions.
-
02
Prepare the message
Write a relevant follow-up and review it before sending.
-
03
Handle the reply
Stop the sequence when someone replies or opts out, and notify you.
-
04
Track the next step
Record conversations and opportunities so you can judge what helped.
Example workflow. A follow-up creates an opportunity for a conversation, not a guaranteed booking.
Discuss this workflow
Review requests
Make honest feedback easier to leave.
For businesses that finish good work but forget to ask for feedback. Give every eligible customer the same straightforward review opportunity.
-
01
The job is complete
An agreed completion event starts the request.
-
02
Ask at the right time
Send a neutral request for an honest review.
-
03
Keep access equal
Offer the same review link to everyone, with a separate support option.
-
04
Stay informed
Track requests and responses without filtering people by their rating.
Example workflow. No incentives, five-star requirement or diversion of unhappy customers.
Discuss this workflow
A different repeat job?
Start with the work
Start with the work
you wish you could hand over.
Daily updates, internal handovers, invoice reminders or preparing a quote. We map the job first, then work out what should run automatically and where you should stay involved.
-
01
A clear first scope
One recurring job, its inputs, the expected result and the tools it touches.
-
02
A price before we build
Setup, timeline, ongoing care and third-party usage costs are explained in your proposal.
-
03
Practical controls
Approval points, failure handling and a way to see what has happened.
-
04
A handover you can use
Access to the custom workflow and a walkthrough, with ongoing help scoped if you need it.
How Digital Artifacts uses this
Our own enquiry workflow.
The configured flow reads business context, prepares a draft reply and asks Isaiah to review it before sending. It is a narrower example than a full booking system: the human still handles the conversation. The form below starts that enquiry process.
The aim is simple: give each enquiry a useful response, with a person reviewing what goes out.
From first conversation to working system
Start with one useful improvement.
A clear scope, a build you can review, and a handover you can use.
Find the sticking point.
We look at what happens today and agree on the first thing worth improving. You receive a scope and fixed project price.
See it before it goes live.
You review the design or workflow. We check real scenarios, including what happens when something goes wrong.
Know what you own.
You get access to the custom code and workflows, with a walkthrough. Ongoing care and third-party costs are agreed separately.
Before you start
A workflow should fit
A workflow should fit
the way you work.
We can begin with a short conversation about the recurring task. You do not need to arrive with a diagram or a list of software.
Does every workflow need AI?
No. Fixed rules work well for many jobs. AI can help with drafting or interpreting information, with review and limits appropriate to the task.
Can you work with my existing tools?
We check how your tools can connect during scoping. Some support direct integrations; others need a different approach. The proposal names what is included.
What happens if a step fails?
Failure handling is part of the scope: what gets retried, what is recorded, and who is notified. We test these paths before handover.
Can I expand it later?
Yes. Start with a useful workflow and review how it performs. Further workflows can be scoped separately using the context and connections already in place.
How does the four-layer framework fit?
It separates business context, task instructions, workflow triggers and the interface you use. It helps keep a larger system understandable as it grows. Read the short explanation.
A useful first conversation
What needs to work better?
Tell me what you have and what is getting in the way. You do not need a technical brief.
Prefer email? hello@digitalartifacts.com.au
Brief received
Thanks. I’ll take a look.
Your brief has been received. I’ll reply within one business day to talk through the next step.
If you need to add anything, email hello@digitalartifacts.com.au.
How your details are used
Your brief is sent to our enquiry workflow and Formspree, a backup delivery service. It may be processed with AI to help draft a response, which Isaiah reviews. Your details are used to respond to your enquiry. Please leave out passwords and sensitive client information. Email hello@digitalartifacts.com.au with questions about your details.