Stuck on the stats chapter of your thesis or manuscript?

Data analysis usually takes longer than expected, and it often lands right when everything else in your program is also due. Handing off the statistics chapter frees up your time for the writing and the defense.

Running a test is one thing, knowing what the p value, the confidence interval, or the model coefficients actually mean for your question is another. I explain the output in plain language you can use in your results section.

If you already ran something and just want someone to check it before you submit, that's usually a smaller project than starting from scratch, and it can catch a mistake before your committee does.

Missing values, unbalanced groups, repeated measures, mixed data types. These are common, not a sign you did something wrong, and they usually just need the right approach.

Reviewers and committees ask pointed questions about methods. I can help you anticipate what they'll ask and have the answer ready.

It's not enough for a result to look right, it needs to hold up when someone asks why you chose that test. I pick methods that fit your design and can explain the reasoning behind each choice.

Not every program teaches R or provides an SPSS license. I can work in whichever tool you already have access to, or the one your data is already in.

Whatever you and your department already work in, R, SPSS, or Python. If you're not sure, tell me what your data is in and we'll go from there.

Yes. Getting help with data analysis is a normal part of research, the same way people work with a writing center or a methodologist on their committee. I run the analysis and explain it, but you're still the one who understands your study, defends it, and writes the discussion. I don't write dissertations or submit work on a client's behalf, and that's stated plainly in the footer of this site.

Depends on scope, but most thesis level analyses come back within a few days to a week once I have your data and a clear question. You'll get a specific timeline with your quote.

I'll give you a written explanation of what was done and what it means, in language you can adapt directly into your methods and results sections. I won't write your discussion or interpret your findings within your field's literature, that part is yours.

Yes. Nothing from your project gets reused, shared, or referenced in any other project.

That's fine, most people I work with aren't statisticians. I explain what a test does and why it fits your question, not just the raw output.

Yes, that's actually one of the most common reasons people reach out. Send the feedback along with your data and I'll address it directly.

Yes. I calculate the sample size your design actually needs and write out the justification, the kind reviewers and ethics committees expect to see before data collection starts.

Yes. Ordination, diversity indices, and community-level tests like PERMANOVA are a regular part of the ecology and biodiversity work I do, always with the assumptions checked and the output explained in plain language.

Yes. I build Power Query pipelines to import and structure raw data automatically, and VBA macros for repetitive tasks like report or invoice generation, with commented code so you can maintain it yourself afterward.

Both. If you've already run something and just want a second set of eyes, that's usually a smaller, cheaper project than starting from zero.