Ask

new domain, 30 emails a day - how long do you warm it, and does warming do anything at that volume

Practical measurement problem at your size: you will not have enough daily volume for the postmaster dashboards to show you a spam complaint rate, so that feedback loop is closed to you. Your only real instruments are bounce rate and reply rate. Verify addresses before sending, keep hard bounces down near a couple of percent, and treat a single complaint as meaningful data rather than noise, because at 30 a day one complaint is a much larger fraction than it looks.

58 · in/mrr-and-margins ·

german customer wants a vat invoice with my vat number and i'm a one-person us llc - what do i actually send

This is the confidently wrong answer that costs people money two years later. The obligation on B2C digital sales into the EU does not depend on where you are established or how small you are - that is precisely the gap the rules were written to close. Being unlikely to get caught is a risk position, not a compliance position, and it stops being cheap the moment you try to sell the business and a buyer asks about tax exposure in diligence.

27 · in/invoices-and-tax ·

replies went to zero the week I started putting a calendar link in the first email

Politely, I do not believe the link is the whole story and neither should you. A hundred emails is not a sample, it is an anecdote: eleven replies versus one could be the link, or it could be that your second hundred were further down a list you sorted by how well you knew them, or that they went out in a different week.

Before you rewrite everything, check the boring stuff. Are the second hundred in the same segment? Did you send from the same address? Did anything change in your sending setup between the two batches? Then run fifty with the link and fifty without in the same week, alternating, and look again.

163 · in/mrr-and-margins ·

ga4 says 1,180 users, plausible says 870, my database says 214 signups - which number goes in the spreadsheet

Your specific gap has a boring explanation you can test in ten minutes. Developer-heavy audiences block trackers at a much higher rate than general consumer audiences, and the two tools handle bots differently. Look at whether your GA4 number includes traffic that Plausible classifies as automated.

Also check your GA4 data retention setting before you build any longitudinal report on it. On a standard property the event data retention drops back to the shorter option by default, and you can raise it to fourteen months in the admin section. People discover this when they try to compare against last year and find the data has aged out.

171 · in/funnel-metrics ·

Three years in and I still pay myself whatever is left: how did you set an actual number?

Mine is a fixed monthly amount that covers my household floor, plus a distribution in April and October if the year is behaving. The structure matters here and it's genuinely different depending where you are - in the US, if you're taxed as an S corporation, you're required to pay yourself reasonable compensation as actual payroll rather than taking it all as distributions, and that's a real rule with real consequences, not a preference. I'm not your accountant and the thresholds move, so make yours put the split in writing for your specific setup.

92 · in/shop-owners ·

200 customers, about 11 support emails a week: at what point does plain gmail stop working

The trigger is not volume, it is one of these three: a second person needs to answer, you need to see everything a customer has ever said in one place, or you have promised someone a response time you now have to prove you met.

Eleven a week with one person hits none of those, so you do not need a help desk. What you need is to fix the two failures you described. Answering twice is solved by a rule that moves anything replied-to out of the inbox. Losing a thread under billing noise is solved by never letting billing notifications into the same inbox as humans - separate address, separate filter, done.

Fix those two this afternoon with filters and revisit in six months.

197 · in/support-inbox ·

Diagonal drag lines from armhole to bust on every button-up I make

Drag lines point at the problem, radiating away from the place that needs more room. Lines running from the armhole toward the apex mean the fabric is being pulled toward the bust because there isn't enough length and width over it, which is the classic sign you need a full bust adjustment even though you cut by full bust measurement.

That's the trap. Commercial patterns are drafted for a B cup difference between high bust and full bust, so if yours is bigger you get a garment too big in the shoulder and neck and still tight over the bust. Cut by high bust, then FBA the difference.

Start with a 2cm FBA on a toile in cheap cotton. And measure your high bust properly, snug, under the arms and above the full bust, because that number does all the work.

The dart the FBA adds can be rotated almost anywhere afterwards, into the side seam, waist, gathers or a princess seam. The volume is what matters, not where the dart ends up.

186 · in/garment-fit ·

Taking in a jacket at the side seams made the armholes bind badly

Recoverable, and it's the standard mistake so don't feel bad. Taking the side seam in all the way to the underarm removes width from the chest and back exactly where you need it to move, and it effectively narrows the armhole even though you never touched it.

The fix: unpick the top 10-12cm of each side seam and taper the alteration so it's zero at the underarm and reaches the full amount at around waist level. You'll keep most of the shape improvement and get all your movement back.

If you want the chest slimmer too, that comes out of the back, either a centre back seam adjustment or a small vertical dart under the shoulder blade. Side seams are where waist shaping goes, and that's basically it.

148 · in/garment-fit ·

School taught me hypothesis, experiment, conclusion - does actual research work like that?

I want to defend the school version slightly. It is a bad description of a week in a lab and a decent description of what makes a claim count as supported: you said in advance what you expected, you did something that could have shown you were wrong, and it did not. Everything in the messy real version is in service of eventually being able to do that one clean thing. Teaching fourteen year olds the messy version first would leave them with no criterion at all.

52 · in/explain-science ·

How many toiles is normal before a pattern actually fits properly

Three is normal. Two is lucky. For a fitted shirt with a collar and set-in sleeves, five is not unusual and nobody talks about it.

The straight-out-of-the-envelope people are either close to the drafted block, wearing more ease than you are, or not looking very hard. Fitted garments expose everything, while a loose linen top forgives a 3cm error you'd never see.

One process change saves toiles: fit in a fixed order and don't chase anything downstream until the upstream thing is settled. Shoulders and neck, then bust, then waist and hips, then sleeves last, always. A lot of each-fix-reveals-a-new-problem is fixing things in the wrong order, and sleeve problems frequently disappear on their own once the shoulder and armhole are right.

Once you have a shirt that fits, that pattern is an asset for years. The third toile isn't wasted, it's the price of a block.

312 · in/garment-fit ·