Nick Franck retweeted
Opening up my calendar for contract work — agentic AI systems, LLM integration architecture, platform engineering, interface design.
I've built:
→ Production RAG + deterministic context assembly
engines
→ Declarative schema tooling for agent loops — validation and transformation as first-class, LLM-readable contracts
→ Automated, policy-enforced software delivery for a large engineering org
If you're building something in this space, DM me. RTs appreciated 🙏
Nick Franck retweeted
Fun fact: the wedding industry in just the United States is 4-5x larger than the global cyber insurance industry (~70-80bn USD vs ~15-20bn USD)
Nick Franck retweeted
Go make a free account on lead.dev rn for a free 36 DR dofollow backlink.
Takes 2 minutes.
You have no excuse 🫡
Nick Franck retweeted
Nick wrote about the stuff. ✍️
He then published & syndicated the writing about the stuff. 👨💻
Then he built links to the stuff. 🔗
Now he's making a lot more stuff. 💸
1 year post @acquiredotcom SaaS acquisition
July 2024 revenue was 5.5x July 2023 revenue
Read this if you want to learn from my mistakes so you can grow faster
Key decision points:
SEO focus- wrote articles, improved technically, got backlinks (follow @ConnorShowler for link ideas). This takes time and is boring BUT it is a $1k/hr task and pays off over time
Partner buyout- Originally bought the SaaS with 2 others. 6 months in had to buy out one partner. Trust your gut. More partners = more risk. Operating agreements matter
Marketing focus- if you are a technical founder, eventually reality sets it. Code doesn't matter. Marketing does. Writing blog posts and making content will actually make you money. Optimizing your DB query to reduce load times doesn't matter in 99% of cases. We wasted A LOT of time on code users don't care about.
Focus- it is easy to get distracted. We started a second app in January. It's doing well, but building it was a distraction. We hadn't fully accepted that we just needed to do marketing instead of building
Do something daily- @thepatwalls is repetitive. "2 hours of deep work every day." But he is right. You might not finish everything you need to in a day. Repeat this daily over a year though and you're bound to get somewhere. Unfortunately most people won't listen to him
I haven't done a great job tweeting updates so I'll work on that. Follow if you're interested
Big shout out to @agazdecki. Investing in an acquire membership is definitely the highest ROI decision I've made
Nick Franck retweeted
CONTENT 🎥🎥
CONTENT🎥🎥
CONTENT🎥🎥
Attention is the new OIL and your Brands online presence is your pipeline🚀🚀
We customize street interviews to your BRAND. Creating authentic, and entertaining ads, posted DAILY across all your socials😳😳😳
We’re already trusted by BILLION dollar brands 💵💵💵
Want to ride the wave, while you’re still early? 🌊🌊🌊
DMs are open- let’s chat
Nick Franck retweeted
Left Stitch Fix after 10 years
built the data platform for 150 data scientists crunching PBs of data, launched about a dozen data products / algorithms. Built human-in-the loop ML products.
Wild run
Figuring out what's next. Anyone hiring?
(retweet for visibility plz 🙏)
Nick Franck retweeted
Talking to @nfcodes about going from Next.js -> LiveView. His biggest complaint is around colocation of client/server-side stuff. His words: it's much easier to write front-end code with React compared to doing it with LiveView. One complaint is the pattern of having client-side hooks all in app.js - even if they're used in a single LiveView. Would be nicer to colocate them with the LV they're used in.
(I am just the messenger)
Nick Franck retweeted
He asked me politely, but I have not responded to him yet. However, he blocked me instead.
Thanks to @nfcodes for giving such a good response.
xitter.cf/nfcodes/status/1776638…
#buildinpublic #indiehackers
Replying to @adrian_horning_ @DarayuthH
If you're in the business of selling links (which he is), then the value of the link is pretty closely tied to the domain rating.
If the domain rating was 90 it would be worth a lot more than $10.
If it's a brand new with a DR of 0 then the value is closer to $0
Nick Franck retweeted
Probably not the "real" Q* but interesting concept nonetheless. My understanding/summary:
First, I think most people understand that chain-of-thought prompting improves an LLMs ability to reason. But, why? For a "non-optimal" language model, chain-of-thought prompting increases the likelihood of a model producing "correct" continuations. I think this probably arises naturally as a function of training data. Correct answers to complex reasoning problems are likely to show up next to the work/reasoning that produces that answer.
This observation led us to:
1. Chain-of-thought prompting techniques to elicit this reasoning in LLMs
2. Generation of datasets with intermediate rationales for fine-tuning LLMs to produce these rationales naturally without prompting
The challenge with both is that inevitably there are rationales which are out-of-distribution. Additionally, generating valid rationales is challenging and requires expert annotators. So how can we build reasoning into these models implicitly?
This work kind of builds on the idea of introducing a scratchpad, pause tokens, or other meta tokens to a language model "force" a model to think before generating a response. They do this in 3 steps:
1. Think. Generate rationales. Rationales are inserted between <|startofthought|> and <|endofthought|> tokens.
2. Talk. Take the hidden state output from each rationale, and pass through a "mixing head" before passing to the language modeling head to get logits for next token prediction.
3. Learn. Optimize parameters for rationale generation to increase the likelihood of rationales that make correct future text most probable.
Some interesting notes: First, they only tried this with a strong pre-trained language model (Mistral-7B). I'm not sure how or if this would work when training a model from scratch, because the model would not be able to produce strong, valid rationales. They acknowledge, and I agree, that this approach would probably improve the performance of much larger models, just as CoT improves disproportionately with larger models.
Second, because the base model does not recognize the new meta-tokens, IOT force valid thoughts from the get go, they initialize the token embedding for <|startofthought|> and <|endofthought|> to equal the token embedding for the emdash `---` because that generally denotes thoughts in writing. This was my favorite part of the whole paper, and I actually think you see some of the consequences of this choice in their examples. The examples almost read like they belong between emdashes.
They also note that their loss function which mixes the normal language modeling loss with a loss relative to the generated rationales is equivalent in theory to language modeling loss for optimal language models. Empirically though the result is a more capable model. They use REINFORCE to optimize a model to produce valid rationales. My understanding here is that they reward rationales which make correct continuations more probable.
There are stability challenges with this approach. One of the most important architectural decisions is how to incorporate thoughts with talk. They do this with their mixing head, but experimented with some other methods as well. I'm pretty sure this is a somewhat common thread in every reasoning-based paper I've seen, I guess because it is literally the central problem in reasoning.
I've slowly been consuming some of the papers out there on building reasoning into language models. It's interesting to see how connected all of these ideas are, and it definitely feels like there's something "in the air" w.r.t. reasoning breakthroughs.
Nick Franck retweeted
v0.0.5 is a big release for instructor!
- GPT-4 Vision support
- @ollama and @togethercompute support
- Better HTTP defaults for streaming
Go check it out #MyElixirStatus
Nick Franck retweeted
12ft is down, @vercel banned me
No warning on a Friday night, while I was on vacation.
Worst yet, they took down all my projects and confiscated all my domains.
No response from support.
Nick Franck retweeted
The early adopters of your product are the ones who are most invested as it's not necessarily proven. Rewarding them with access to influencing the direction of the product is a nice incentive . Great to hear these stories Nick, keep em coming!
Nick Franck retweeted
In preparation for @ElixirConf US and my talk about Nx Powered Decision Trees, let's see if we can get EXGBoost to 100 GitHub Stars. It'd make the slide look a lot better
👉👈
github.com/acalejos/exgboost
#MyElixirStatus
Nick Franck retweeted
Congrats to Nick on his acquisition!
xitter.cf/nfcodes/status/1686511…
Just made my first purchase (SaaS company) on @acquiredotcom with some friends
It was a straightforward but tedious process where we made at least one mistake which I'll mention at the end.
Here is what it looked like overall:
1. Found an interesting company
3. Signed Letter of Intent (LOI) aka made an offer, offer was countered, we accepted the counter
4. Further due diligence (i.e. double checking revenue, expenses, customers, etc.)
5. Signed Asset Purchase Agreement (APA), aka a list of assets like IP, domains, codebase, accounts, etc. that we agreed to purchase for the price proposed in the LOI.
6. Escrow started. We transferred cash to escrow dot com. Seller transferred assets.
7. Purchase complete
Mistake We Made:
Not accounting for deferred revenue (noob mistake I know)
Some customers have prepaid for the service that hasn't been delivered. So the seller got the money but we have to bear the cost.
Looking back we could have negotiated for this deferred revenue or at least accounted for it in our offer.
Fortunately we still felt we were getting a good deal even after accounting for this!
I'll be tweeting more about the purchase process, how we're adding value to our SaaS, and other lessons learned so give me a follow if you're interested.
Thank you @agazdecki for building such a cool platform!
Nick Franck retweeted
Here's a peek behind the curtain of a business acquisition through @acquiredotcom from a friend of mine for those who are curious. Might save you some heartache down the road.
Off to a rough start.
Just after completing my @acquiredotcom acquisition we had a brief outage on the root domain. Likely from some hiccup in the transition process.
Post-transition, we experienced unexpected downtime on the root domain.
Although the www subdomain was fully operational, the root domain – the one indexed on Google – likely remained inaccessible to visitors.
Fortunately, I was able to mitigate this issue by modifying the DNS A record to utilize @Cloudflare's CNAME flattening. By redirecting the root domain to the same destination as the www subdomain, we restored the service.
Still need to investigate why the outage happened in the first place.
Nick Franck retweeted
This makes me sad:
observablehq.com/@ayhanfuat/…
Nick Franck retweeted
ChatGPT for @acquiredotcom.
Coming soon to your favorite startup acquisition marketplace with many awesome use cases that make getting acquired easier for founders.
We're just getting started.
Credit to @sean_moriarity!


















