392 karma · joined April 4, 2012
About me: Coey.dev
Let's connect: github.com/acoyfellow x.com/acoyfellow facebook.com/coeyman
Self healing, I try two ways:
1) use a memory tool to store learnings for next iteration (Deja.coey.dev) and have the loop system instructions tell how to use it. One orchestrator, and sequential worker agents who run til their context is full and then hand off to the next run with learnings
2) the agent Shelley on exe can search past convos when promoted too for continuation.
I’ve been doing this with great success just “falling” into the implementation after proper guardrails are placed
I agree. that's next on my list. Wanted to get it out there early. Thanks for checking it out!
If you're still interested, please take another try... I've got more visibility into logs and errors, and it should be much more reliable!
I plan on adding it soon, after smoothing out the internals.
edit: problem found, fixed, and tested.. let me know if you have a chance to try again
I use it everywhere. Optkit.com
One of his most repeated tasks is helping clients predict their cash flow...
So, this tool to simplify and automate that process, making it accessible to everyone. Next steps are going to be exploring some revenue opportunities.
It's rough around the edges (it literally could not be a simpler prototype), but I'm curious about its potential to evolve email beyond its current state.
Keen to explore how AI could make email a more powerful tool?
I'd love to hear your thoughts or see you give it a whirl by emailing hello@inbox.dog
Cheers,
- Jordan
I'd love feedback on the idea, and the main two use cases: sales & support. This system requires no real phone, only a web browser (webrtc p2p video + screen sharing).
I was inspired to build this by a comment with a partner (on another SaaS): "if i have a team i want to scale quickly, they should be focused on 1 thing and 1 thing only"...
They do a lot of online marketing with funnels, and close deals over the phone. They use a mix of sales pages, and close deals over the phone.
So with CallKite their team of sales team can all actively answer questions of potential buyers, right there live on a sales page as if they were over their shoulder or in real life. They can sit down from anywhere with a browser, and just start answering calls.
I have a lot of ideas of where this product could go, but I wanted to get a usable and simple version out the door A.S.A.P. Thanks for checking it out!
Tech stack:
* Sapper/Svelte
* Tailwind
* Google/Firebase: Functions, Firestore, Auth
* Cloudflare: cdn, workers/kv
* Stripe: payments
The entire project (auth, database, payments) comes in normally under 200kb per page, even the heart of the application (the form editor) comes in @ 59kb. Nearly 100's across the board in Lighthouse.. Only a few accessibility issues with the homepage. I'm also experimenting with a mix of exporting sapper and using firebase functions for SSR. If no static file is found in Cloudflare, it falls back to the Firebase SSR / Sapper route.
Any questions or feedback let me know.
> Homepage: https://calcmaker.com/
> No-signup Demo: https://calcmaker.com/playground/RxILjYhXs0JcHNPaYhTt
> Example of the end form: https://calcmaker.com/-/RxILjYhXs0JcHNPaYhTt
My answer:
Client X is a SaaS. They have all marketing pages on "root.com"
Their signup flow is on "accounts.root.com"
Their actual SaaS app (which has Mixpanel installed) is on: "app.root.com"
Outline of Problem:
- You want to drive traffic to their homepage (root.com, root.com/case-studies...)
- You want to use UTM variables to track ad performance from Google Ads.
- You have to get those UTM variables down into "app.root.com" (and inside mixpanel)- so we know which people are attributed to which campaigns/sets/ads.
This tool is allowing me to do what I need: Attribute.pro - it allows me to drop a tag on "root.com", use UTM links, then re-call those UTM links from "app.root.com" (or any other domain)
How would you solve this problem?
Why? I needed a solution for a client, and I wanted to make it re-usable.
Built with 1 single Cloudflare worker. No server, no database.
Have any suggestions on what to call it, in this early version?