Your team runs on Obsidian and it does almost everything you need. I build the part it's missing, and I have a plugin that passed Obsidian's public review.
Your team runs on Obsidian. It does almost everything you need, except the one thing that would save an hour a day. Nobody built it as a public plugin because your workflow is specific to you.
That's what I build.
I'm published, not just capable
S-Calc is my Obsidian plugin, listed in the official community marketplace. Write expressions in an s-calc code block and each line's result appears inline in your theme's accent colour, live as you type. It handles arithmetic, variables, percentages, unit conversion, live currency rates, and plain-language dates. TypeScript, mathjs, chrono-node, and CodeMirror 6, released under MIT and in public use.
Getting into that marketplace means an independent reviewer read the code and the security model and approved it. Most developers who tell you they can build an Obsidian plugin have never had one accepted anywhere. That is the difference you are paying for.
I also run Obsidian as my own daily vault, so I already know where the API is awkward. I'm not learning your tool on your budget.
What I build
Internal tooling. Your team's process, inside the vault they already live in. Nobody learns a new app.
API and data integrations. Pull your CRM, database, issue tracker, or internal service into a note so people stop alt-tabbing to a dashboard.
Custom views and editor behaviour. CodeMirror 6 work, live preview rendering, custom panels. This is the deep end of the API and it is where most plugins fall over.
Public plugins. Something you want to publish under your own name, built to survive community review the first time.
How it works
- A call. You show me the friction. Free, 30 minutes.
- Scope. What it does, what it doesn't, what it costs. In writing, before you commit.
- Build. You get something installable in your vault by around week two.
- Handover. Source, docs, and a build you can publish or keep private.
What you get
The code is yours. Documented well enough that another developer can maintain it without me, because a plugin only one person understands is a liability, not an asset.
Ready to start?
Tell me what your team keeps doing by hand. If a plugin isn't the right answer, or an existing one already covers it, I'll tell you that on the call and charge you nothing.
Reach me by email, on LinkedIn, or fill in the form on this page.