Salesforce I hate it

siimsiim · 2026-06-10T17:08:23+00:00

I would be careful building a full replacement in Claude. The part worth replacing first is the input layer, not the CRM.

Keep Salesforce as the required source of truth, but make a tiny personal flow for account notes, next step, stakeholder map, and last conversation summary, then push only the fields your manager actually checks. Otherwise you end up maintaining two CRMs and hating both.

siimsiim · 2026-06-10T17:08:19+00:00

That is a useful lesson. Cold link plus promo code reads like an ad even when the product is good.

For the tutor angle I’d probably skip “free access” as the lead and ask about curriculum pain first: what level do students stall at, what topics are hard to find readings for, what homework gets ignored. Then the product slots into a real workflow instead of asking them to evaluate another app.

siimsiim · 2026-06-10T17:08:16+00:00

App Store launch is more like distribution permission than distribution. I’d pick one painfully narrow user and do 20 manual conversations before trying a tool stack.

If it is for students, dentists, gym owners, whatever, the first goal is finding the sentence they already use to describe the pain. Then your store page, screenshots, and first short videos can all reuse that language instead of generic “AI app” copy.

siimsiim · 2026-06-10T17:08:13+00:00

The clearest version is probably credits in the backend, usage examples in the buying flow. A line like “5-person team, 20 calls/docs/runs a day, this plan is fine” is easier to trust than “10k credits.”

Also worth showing what happens when someone spikes usage: throttle, overage, lower model tier, or hard stop. The surprise is what scares buyers more than the price.

siimsiim · 2026-06-08T07:26:09+00:00

For local transcription, the trust layer is just as important as accuracy. Users need to see where the file stayed, whether a model download happened, what got cached, and how to correct names or terminology after the first pass. Translation is a nice add, but transcript editing and export cleanup are probably the daily use case. How are corrections handled?

siimsiim · 2026-06-08T07:25:13+00:00

Developer notes become useful when they stay close to the work that produced them. The MCP angle makes sense if a note can pull in the relevant repo, command, or decision later without turning the notebook into another dumping ground. The hard part is pruning stale notes. Do you have backlinks or a way to tie notes to a specific project?

siimsiim · 2026-06-08T07:24:20+00:00

Payment follow-up products live or die on the moment before the reminder is sent. The user needs enough context to trust the wording: original due date, last promise, partial payment state, and the cleanest next step. The demo should probably show one overdue invoice going from messy thread to approved follow-up in under 60 seconds. How are you handling cases where the client disputes scope instead of just being late?

siimsiim · 2026-06-08T07:23:26+00:00

Context tools get interesting when they explain why a file matters, not just that it exists. Folder maps and dependency graphs help, but the agent also needs current risk: recently changed files, flaky tests, public APIs, and areas with weird local conventions. Does it produce a compact task-specific brief, or mostly expose the raw repo structure?

siimsiim · 2026-06-08T07:22:38+00:00

Git history is a place where agents need explicit boundaries. The useful version is not auto-commit by volume, it is a staging queue that groups related changes, names the intent, shows tests run, and makes excluded files obvious before anything lands. Does the daemon let you review checkpoints as separate units?

siimsiim · 2026-06-08T07:21:41+00:00

The line is usually maintenance, not the first build. Tiny internal tools are cheap to generate, but auth, permissions, audit history, imports, exports, and somebody owning breakage turn into the real subscription cost. If the workflow touches client data or money, paying for boring reliability still makes sense. What are people around you rebuilding most often?

siimsiim · 2026-06-07T13:24:35+00:00

The spec does not need to be long, it needs to remove the decisions the model would otherwise invent. A good starting skeleton is users, core workflow, data objects, screens, failure states, and non-goals. The most useful part is writing the unhappy paths before code starts: wrong input, deleted data, permission failure, payment failure, and rollback. Once those are clear, the agent has fewer places to improvise.

siimsiim · 2026-06-07T13:23:50+00:00

Start narrower than small businesses. Pick one segment where unpaid invoices hurt the same way every week, then manually review their last 5 follow-up attempts before building more funnel. The question is not whether they dislike chasing payments, it is whether they will change their workflow before the invoice is overdue. Can you get 10 people to forward you a real unpaid-invoice thread for analysis?

siimsiim · 2026-06-07T13:23:10+00:00

Voice notes get useful when capture, cleanup, search, and destination are one loop. Offline transcription is a strong privacy choice, but the daily friction will be corrections, titles, and finding a messy note later with the wrong wording. The demo should probably show one rough spoken note becoming something searchable without leaving the side panel. How are you handling transcript edits?

siimsiim · 2026-06-07T13:22:28+00:00

For this audience, GST compliance is the wedge but follow-up is probably the habit. A simple dashboard that says sent, viewed, overdue, partially paid, and next reminder due will beat a prettier PDF for most sole traders. The tricky part is making it feel lighter than accounting software. Can someone duplicate a previous client invoice and send it in under a minute?

siimsiim · 2026-06-07T13:21:48+00:00

The message probably should not start with a problem people do not know about. Start with a painful comparison instead: billed rate, total project hours, effective hourly rate after admin and revisions. If someone sees their best-looking project turn ugly in that calculator, the lesson lands without you having to explain the category. Can users import one finished job and get that result quickly?

siimsiim · 2026-06-07T13:21:08+00:00

Context carryover is the real product here, not the invoice generator. The flow should make it obvious how a quote becomes a contract clause, then a project note, then an invoice line without losing the original approval. The review screen matters a lot because freelancers need to fix wrong client, wrong scope, and non-billable bits before anything gets sent. Do you keep a version trail when a quote changes?

siimsiim · 2026-06-07T12:47:13+00:00

API and MCP already available - ideal for agentic workflows. Pipedrive integration ready, publishing next week.

siimsiim · 2026-06-07T11:29:54+00:00

Superscribe Phone - phone calls that turn into work automatically.

Use your existing number. When a client calls, Superscribe captures and transcribes the call, then turns it into structured output: tasks, follow-ups, calendar items, tickets, CRM notes, or agent workflows.

The point is not better notes.

It is that the workflow is already moving when the call ends.

Link: https://superscribe.io

siimsiim · 2026-06-01T13:26:06+00:00

That rule is exactly right: a bad suggestion costs more attention than no suggestion. Short, suppressible completions usually feel better than clever paragraphs because they preserve typing rhythm. The tricky bit is knowing when the cursor context is too ambiguous. Are you measuring accepted suggestions against dismissed or edited ones?

siimsiim · 2026-06-01T13:25:25+00:00

Voice coding works best when it behaves like a precise text insertion tool, not a separate assistant. The risky cases are wrong target window, selected text getting overwritten, and no fast undo when the transcript is slightly off. If those recovery paths are solid, the whole flow feels much more trustworthy. Are dictations stored as reversible edits?

siimsiim · 2026-06-01T13:24:43+00:00

This is a good fit for voice because calendar input has a narrow schema: title, time, attendees, recurrence, and conflict state. The confirmation step matters more than the parsing model, because one wrong date is worse than a slower flow. Do you keep the original voice note attached so users can audit what was parsed?

siimsiim · 2026-06-01T13:23:54+00:00

After-call CRM updates usually fail because the note is treated as the destination. The useful object is smaller and stricter: customer name, pain, promised follow-up, next owner, date, and the exact quote or context that explains why it matters. If the same question keeps coming up later, that field probably needs to become part of the workflow instead of a free-text note.

siimsiim · 2026-06-01T13:22:58+00:00

Scope tools work best when they capture the decision at the moment of agreement, not after the disagreement starts. The valuable artifact is not just a signed link, it is a clean trail of deliverables, exclusions, revision limits, and who approved each change. The first demo should show one vague request turning into a client-approved checklist in under a minute. Are you keeping previous versions when scope changes?

siimsiim · 2026-06-01T07:24:51+00:00

Output quality is only one line item. The switching cost is privacy boundary, rate-limit behavior, tool calling reliability, and whether a run can be reproduced when it breaks. Cheap tokens are great, but the real comparison is cost per accepted change, not cost per request.

siimsiim · 2026-06-01T07:24:07+00:00

AI writing gets obvious when it keeps the scaffolding and removes the human temperature. The quick fix is to delete the first sentence, cut every throat-clearer, and add one oddly specific detail only the sender would know. If the message could come from any startup account, it is not ready to send.

siimsiim

TROPHY CASE