Reckonworks
We help you explore with AI.
Scattered to sharp. That's how reckon works.
A reckoning
The dot is the whole story
SoftSharp
SharpSoft

Our logo morphs between a circle and a diamond. Your skills go from soft to sharp: vague curiosity becomes precise capability. But your nerves go the other way: the edge comes off, the overwhelm fades, and what's left is clarity. The shape keeps moving because the work never really stops. You just get better at it.

Reckon
/ˈrek.ən/
Old English gerecenian — to recount, explain, arrange. From Proto-Germanic *rekenōną — to count, make ready.
verb noun phrase
1
reckon with phrasal verb

To confront or come to terms with something difficult or significant. To take seriously as a factor or force. Often implies something that can no longer be ignored.

"Any business that hasn't reckoned with AI is already behind."

also: to be reckoned with

To be taken seriously. Someone or something with real weight, not easily dismissed.

"She came back from the workshop a force to be reckoned with."

We help people reckon with AI. Honestly, practically, without the jargon.
2
reckoning noun

The act of calculating or estimating something. A settling of accounts; an honest evaluation of a situation, especially one that has been avoided or postponed.

"A day of reckoning for how the team actually spends its time."

archaic: dead reckoning

Navigating by calculation from a known position, without external reference points. Working with what you have, where you are.

A reckoning is just an honest look at what's there. We start every session with one.
3
I reckon phrase, informal

To think or suppose, based on experience rather than certainty. Carries a tone of considered, grounded opinion. More deliberate than "I think", less formal than "I believe".

"I reckon you could cut that process in half."

regional note

Common in Australian, South African, and Southern American English. Implies someone who's done the thinking, not just the guessing.

We reckon AI works best when people stop reading about it and start using it.
The gap

Most people haven't reckoned with AI yet. Not really.

Someone on your team uses ChatGPT for emails. Someone else ran a prompt workshop that felt like a college lecture. The tools are everywhere, but the confidence isn't.

The real gap is between curiosity and capability. Between "I should use AI more" and actually opening it at 9am on a Tuesday with your real work in front of you, and knowing exactly what to do.

A reckoning is just an honest look at what's there and what's possible. We help individuals figure out their own workflow, entrepreneurs build something new, and teams get everyone moving in the same direction. We reckon it works.

What we cover

The right tool for your actual work

We teach AI as a platform, not a party trick. Right now that means deep work with the most capable tools we've found for professional use. But AI moves fast, and so do we. What matters is that you learn to think with these tools, not just click through them.

Think & write
Conversational AI
Projects that organize your context. Artifacts that let you iterate. Memories that mean you stop repeating yourself. An AI that keeps up with how you actually think.
Browse & extract
Browser agents
If it opens in a browser, AI can work with it. Fill forms, pull data, compare across tabs. Your browser becomes a workspace, not just a window.
Automate & connect
Desktop agents
Agents that plug into Slack, Jira, Google, MS365, and 30+ other tools. File organization, document generation, workflow automation. From chatbot to coworker.
Build & ship
Coding agents
Plain English in, working software out. Read entire codebases, write and edit code, run builds, handle version control. Move faster without cutting corners.
Reckon Day

One day. On-site. Hands-on.

A Reckon Day is built around your team's actual work. We show up, look at how you operate, and spend the day transforming workflows into better ones. Not slides about the future. Tools you'll open again tomorrow.

Morning
Audit what's real, cut through the noise
We start with how your team actually works, not how you think you should be using AI. Honest assessment. Which model for which job, which tool for which task, where the real leverage is. No hype, no guilt.
Midday
Hands on keyboards, your actual tasks
Live demos, then you do it. Real tools, real workflows, your actual codebase or documents. Meeting transcripts turned into structured minutes. Browser tasks automated. Code reviewed and refactored. Things you keep, not things that expire when the workshop ends.
Afternoon
Practice until it sticks
You practice with your own work until the muscle memory forms. We map each person's takeaways, what to try first, what to ignore. You leave with a reference guide and skills, not slides and good intentions.
After the day

What actually changes

01
The right tool, immediately
Your team stops guessing. They know which AI tool to reach for, which model to use, and when to skip AI entirely.
02
Workflows, not workarounds
Current processes become optimised ones. Meeting minutes from transcripts. Browser tasks automated. Code reviewed in seconds. Running on Monday, not "someday".
03
Confidence over curiosity
The gap between "I should use AI" and "I just did" closes. Every hour saved goes back into the work that actually matters to you.
Reckon Retreat

Some things need more than a day

The Reckon Retreat is a multi-day immersion away from the office. Mornings are practical. Afternoons are for the thinking that makes the practical stuff stick. Clarity comes before capability.

When you step away from the noise, you see the patterns.

Coming soon
Who we are

Two people who use this stuff daily

Reckon. is Bas de Beer and Rudie Verweij. We've spent the past year building with AI every day. Not advising from a distance. Building, shipping, iterating. We teach what we actually do.

Bas de Beer

Designs experiences and runs the room. Spent years making complex things feel simple, now doing the same with AI. Cares more about what happens after the workshop than during.

Rudie Verweij

The technical backbone. Builds the systems that make AI work in practice, not just in theory. If there's a smarter way to solve a problem, he's probably already shipped it.